Network light switch with mechanical/electrical interface port

ABSTRACT

A network device for controlling an electric light or other remote electrical device. In addition to features found in standard light switches, such as cover plates, housings, switching elements, and internal wiring, the network device may include a cover plate with embedded cover circuitry for performing advanced functions unavailable to standard light switches. Functions performed by the cover circuitry include advanced electrical communication, data processing, user interfacing, sensing, displaying, rule creation, and the like. The cover circuitry may receive electric power via a set of contact elements located on the wall-facing side of the cover plate that electrically couple with a similar set of contact elements located on the room-facing side of the housing. The coupling of contact elements may form a set of buses that enable data communication between the cover circuitry and circuitry within the housing.

BACKGROUND

Traditionally, installing a light switch included connecting a switchwith wiring in a building. If a person wanted a light switch to beplaced at a new location, it was conceivable that existing wiring in abuilding could prevent such positioning. Even if such positioning wastechnically feasible, it would frequently involve cutting through walls,running cable, and appropriately connecting wires. Such tasks can bemessy, intimidating and even dangerous for inexperienced people.

BRIEF SUMMARY

In a first embodiment of the present disclosure, a network device isprovided. The network device may include a housing configured to bemounted into a wall. The housing may include a room-facing side and awall-facing side. The housing may include electrical connections forcoupling with a line power. The housing may include a set of housingelectrical contact elements located on the room-facing side of thehousing. The network device may include a cover including a room-facingsurface and a wall-facing surface. The wall-facing surface of the covermay be configured to be removably attached to the room-facing side ofthe housing. The cover may include a set of cover electrical contactelements located on the wall-facing surface of the cover. The cover mayinclude cover circuitry configured to receive an input signal. The covermay be attachable to the housing. The cover circuitry may beelectrically coupled with the set of cover electrical contact elements.The set of housing electrical contact elements may be electricallycoupleable with the set of cover electrical contact elements. The one ormore elements on the room-facing side of the housing may be physicallyaccessible through an opening defined by the cover.

In some embodiments, the cover circuitry may be electrically coupledwith the line power via the set of housing electrical contact elementsand the set of cover electrical contact elements. In some embodiments,the network device includes an antenna located within the covercircuitry for communicating with an electrical device. In someembodiments, the network device includes a processor located within thecover circuitry. The processor may be configured to perform operationsincluding receiving the input signal and transmitting a signal to modifya state of an electrical device. In some embodiments, the set of housingelectrical contact elements may be in physical contact with the set ofcover electrical contact elements and form a USB connection. In someembodiments, the set of housing electrical contact elements may be inphysical contact with the set of cover electrical contact elements andform a set of buses. The set of buses may include a first bus, a secondbus, and a third bus. In some embodiments, the processor may be furtherconfigured to perform operations including using the first busexclusively for receiving data from housing circuitry. The housingcircuitry may be located within the housing. The processor may befurther configured to perform operations including using the second busexclusively for transmitting data to the housing circuitry. Theprocessor may be further configured to perform operations includingusing the third bus exclusively for electrically coupling with the linepower. In some embodiments, the cover circuitry may include a sensorlocated on the room-facing surface of the cover. The sensor may beconfigured to output a sensor reading related to controlling a state ofan electrical device. In some embodiments, the sensor includes atemperature sensor.

In some embodiments, a computer-implemented method is provided. Themethod may include receiving, by cover circuitry located within a cover,an input signal for controlling a state of an electrical device. Awall-facing surface of the cover may be configured to be removablyattached to a room-facing side of a housing. The housing may beconfigured to be mounted into a wall. The method may includetransmitting, by the cover circuitry, a signal to modify the state ofthe electrical device. The cover may be attachable to the housing. A setof housing electrical contact elements located on the room-facing sideof the housing may be electrically coupleable with a set of coverelectrical contact elements located on the wall-facing surface of thecover. The cover circuitry may be electrically coupled with the set ofcover electrical contact elements. One or more elements on theroom-facing side of the housing may be physically accessible through anopening defined by the cover.

In some embodiments, the method may include receiving, by the covercircuitry, electric power from a line power. The electric power may bereceived by the cover circuitry from the line power via the set ofhousing electrical contact elements and the set of cover electricalcontact elements. In some embodiments, the cover circuitry may includean antenna for communicating with the electrical device. In someembodiments, the set of housing electrical contact elements may be inphysical contact with the set of cover electrical contact elements andform a USB connection. In some embodiments, the set of housingelectrical contact elements may be in physical contact with the set ofcover electrical contact elements and may form a set of buses. The setof buses may include a first bus, a second bus, and a third bus. Themethod may include using, by a processor located within the covercircuitry, the first bus exclusively for receiving data from housingcircuitry. The housing circuitry may be located within the housing. Themethod may include using, by the processor, the second bus exclusivelyfor transmitting data to the housing circuitry. The method may includeusing, by the processor, the third bus exclusively for electricallycoupling with the line power. In some embodiments, the cover circuitrymay include a sensor located on a room-facing surface of the cover. Thesensor may be configured to output a sensor reading related tocontrolling the state of the electrical device. In some embodiments, thesensor includes a temperature sensor. In some embodiments, anon-transitory computer-readable medium may be provided that includesinstructions that, when executed by a processor, cause the processor toperform the computer-implemented method.

In a second embodiment of the present disclosure, a network device isprovided. The network device may include a housing configured to bemounted into a wall. The housing may include a room-facing side and awall-facing side. The housing may include electrical connections forcoupling with a line power. The network device may include a coverincluding a room-facing surface and a wall-facing surface. Thewall-facing surface of the cover may be configured to be removablyattached to the room-facing side of the housing. The network device mayinclude an electronic display located on the room-facing surface of thecover. The network device may include a processor electrically coupledwith the electronic display. The processor may be configured to performoperations including outputting a representation of an electronic deviceon the electronic display. The electronic device may be associated witha state. The processor may be configured to perform operations includingreceiving input corresponding to a selection of the electronic device.The processor may be configured to perform operations includingreceiving input corresponding to a modification of the state of theelectronic device. The processor may be configured to perform operationsincluding transmitting a signal corresponding to an instruction tomodify the state of the electronic device. Receiving the instruction atthe electronic device may cause the electronic device to modify thestate according to the instruction.

In some embodiments, the instruction may cause the electronic device tomodify a power state of the electronic device. In some embodiments, theinstruction may cause the electronic device to modify a physicalposition state of the electronic device. In some embodiments, theprocessor may be further configured to perform operations includingtransmitting an interrogation signal to determine a current state of theelectronic device. The processor may be further configured to performoperations including receiving a response signal indicating the currentstate of the electronic device. The processor may be further configuredto perform operations including outputting the current state of theelectronic device on the electronic display. In some embodiments, theprocessor may be further configured to perform operations includingtransmitting an interrogation signal to determine a current power stateof the electronic device. The processor may be further configured toperform operations including receiving a response signal indicating thecurrent power state of the electronic device. The processor may befurther configured to perform operations including transmitting aninstruction signal to toggle the current power state of the electronicdevice. In some embodiments, the electronic display may include inputelements. The input corresponding to the selection of the electronicdevice may be received by the input elements. In some embodiments, thenetwork device may include a primary switching element located on theroom-facing side of the housing. The input corresponding to themodification of the state of the electronic device may be received atthe primary switching element. In some embodiments, the inputcorresponding to the modification of the state of the electronic devicemay be received by the input elements. In some embodiments, the inputcorresponding to the selection of the electronic device and the inputcorresponding to the modification of the state of the electronic devicemay be received simultaneously. In some embodiments, the cover includesthe processor. In some embodiments, the processor is electricallycoupled with the line power via the housing.

In some embodiments, a computer-implemented method is provided. Themethod may include outputting, by a network device including aprocessor, a representation of an electronic device on an electronicdisplay. The electronic device may be associated with a state. Thenetwork device may include a housing configured to be mounted into awall. The housing may include a room-facing side and a wall-facing side.The housing may include electrical connections for coupling with a linepower. The network device may include a cover including a room-facingsurface and a wall-facing surface. The wall-facing surface of the covermay be configured to be removably attached to the room-facing side ofthe housing. The cover may include cover circuitry including theelectronic display located on the room-facing surface of the cover. Themethod may include receiving input corresponding to a selection of theelectronic device. The method may include receiving input correspondingto a modification of the state of the electronic device. The method mayinclude transmitting, using the network device, a signal correspondingto an instruction to modify the state of the electronic device.Receiving the instruction at the electronic device may cause theelectronic device to modify the state according to the instruction.

In some embodiments, the instruction may cause the electronic device tomodify a power state of the electronic device. In some embodiments, themethod may include transmitting an interrogation signal to determine acurrent state of the electronic device. The method may include receivinga response signal indicating the current state of the electronic device.The method may include outputting the current state of the electronicdevice on the electronic display. In some embodiments, the method mayinclude transmitting an interrogation signal to determine a currentpower state of the electronic device. The method may include receiving aresponse signal indicating the current power state of the electronicdevice. The method may include transmitting an instruction signal totoggle the current power state of the electronic device such that adevice that was previously powered off is powered on and a device thatwas previously powered on is powered off. In some embodiments, theelectronic display may include input elements. The input correspondingto the selection of the electronic device may be received by the inputelements. In some embodiments, a primary switching element may belocated on the room-facing side of the housing. The input correspondingto the modification of the state of the electronic device may bereceived by the primary switching element. In some embodiments, theinput corresponding to the modification of the state of the electronicdevice may be received by the input elements. In some embodiments, theinput corresponding to the selection of the electronic device and theinput corresponding to the modification of the state of the electronicdevice may be received simultaneously. In some embodiments, anon-transitory computer-readable medium may be provided that includesinstructions that, when executed by a processor, cause the processor toperform the computer-implemented method.

In a third embodiment of the present disclosure, a network device isprovided. The network device may include a housing configured to bemounted into a wall. The housing may include a room-facing side and awall-facing side. The housing may include electrical connections forcoupling with a line power. The network device may include a coverincluding a room-facing surface and a wall-facing surface. Thewall-facing surface of the cover may be configured to be removablyattached to the room-facing side of the housing. The cover may includecover circuitry. The network device may include a sensor configured toprovide a sensor reading. The network device may include a processorelectrically coupled with the sensor. The processor may be configured toperform operations including receiving the sensor reading. The processormay be configured to perform operations including evaluating a rule. Therule may use the sensor reading. The processor may be configured toperform operations including determining that an instruction signal isto be transmitted to an electrical device. The processor may beconfigured to perform operations including transmitting the instructionsignal to modify a state of the electrical device. The processor may beconfigured to perform operations including receiving the instruction atthe electronic device causes the electronic device to modify the stateaccording to the instruction.

In some embodiments, the instruction signal may include instructions tomodify a power state of the electrical device. In some embodiments, thesensor may be a temperature sensor, a light sensor, a humidity sensor, aproximity sensor, and any combination of these. In some embodiments, therule includes a comparison of the sensor reading to a reference value.The determination that an instruction signal is to be transmitted to theremote electrical device may be made when the sensor reading eitherexceeds or does not exceed the reference value. In some embodiments, thenetwork device may include a primary switching element located on theroom-facing side of the housing. In some embodiments, the operations mayinclude determining that the primary switching element has been pressed.The operations may include upon determining that the primary switchingelement has been pressed, transmitting a request signal to the sensor torequest the sensor reading. In some embodiments, the operations mayinclude automatically obtaining the sensor reading. The operations mayinclude determining that the primary switching element has been pressed.

In some embodiments, a computer-implemented method is provided. Themethod may include receiving, by a network device including a processor,a sensor reading. The network device may include a housing configured tobe mounted into a wall. The housing may include a room-facing side and awall-facing side. The housing may include electrical connections forcoupling with a line power. The network device may include a coverincluding a room-facing surface and a wall-facing surface. Thewall-facing surface of the cover may be configured to be removablyattached to the room-facing side of the housing. The cover may includecover circuitry including a sensor configured to provide the sensorreading. The method may include evaluating a rule. The rule may use thesensor reading. The method may include determining that an instructionsignal is to be transmitted to an electrical device. The method mayinclude transmitting the instruction signal to modify a state of theelectrical device. Receiving the instruction at the electronic devicemay cause the electronic device to modify the state according to theinstruction.

In some embodiments, the instruction signal may include instructions tomodify a power state of the electrical device. In some embodiments maybe sensor is a temperature sensor, a light sensor, a humidity sensor, ora proximity sensor. In some embodiments, the rule may include acomparison of the sensor reading to a reference value. The determinationthat an instruction signal is to be transmitted to the remote electricaldevice may be made when the sensor reading either exceeds or does notexceed the reference value. In some embodiments, the rule may bemodifiable using a touch screen located on the room-facing surface ofthe cover. In some embodiments, a primary switching element may belocated on the room-facing side of the housing. In some embodiments, themethod may include determining that the primary switching element hasbeen pressed. In some embodiments, the method may include upondetermining that the primary switching element has been pressed,transmitting a request signal to the sensor to request the sensorreading. In some embodiments, the method may include automaticallyobtaining the sensor reading. In some embodiments, the method mayinclude determining that the primary switching element has been pressed.In some embodiments, a non-transitory computer-readable medium may beprovided that includes instructions that, when executed by a processor,cause the processor to perform the computer-implemented method.

BRIEF DESCRIPTION OF THE DRAWINGS

Illustrative embodiments are described in detail below with reference tothe following drawing figures:

FIG. 1 is an illustration of an example of a network environment, inaccordance with some embodiments.

FIG. 2 is a flowchart illustrating an embodiment of a process forregistering one or more network devices, in accordance with someembodiments.

FIG. 3 is an illustration of an example of a network environment, inaccordance with an embodiment.

FIG. 4 is an illustration of an example of a network environment, inaccordance with an embodiment.

FIG. 5 is an illustration of an example of a network environment, inaccordance with an embodiment.

FIG. 6 is an illustration of an example of a front view of a networkdevice, in accordance with an embodiment.

FIG. 7 is an illustration of an example of a side view of a networkdevice, in accordance with an embodiment.

FIG. 8 is an example of a block diagram of a network device, inaccordance with an embodiment.

FIG. 9 is a schematic illustration of a local area network including anetwork device that includes an appliance, in accordance with anembodiment.

FIG. 10 is an example of a block diagram of a network device includingan interface device attached to an appliance, in accordance with anembodiment.

FIG. 11 is an illustration of a network device with a virtual interface,in accordance with an embodiment.

FIG. 12A, FIG. 12B, FIG. 12C, FIG. 12D, FIG. 12E, and FIG. 12Fillustrate a series of example interfaces at a device (e.g., an accessdevice) for receiving user input to define a rule, in accordance with anembodiment.

FIG. 13 is an illustration of an example of front and side views of anetwork device, in accordance with an embodiment.

FIG. 14 is an illustration of an example of front and side views of anetwork device, in accordance with an embodiment.

FIG. 15A and FIG. 15B are illustrations of perspective views of anetwork device, in accordance with an embodiment.

FIG. 15C is an illustration of a perspective view of a cover plate, inaccordance with an embodiment.

FIG. 15D is an illustration of an example of a perspective view of ahousing, in accordance with an embodiment.

FIG. 16 is an illustration of an example of a side view of a networkdevice, in accordance with an embodiment.

FIG. 17 is an example of a block diagram of a network device, inaccordance with an embodiment.

FIG. 18A, FIG. 18B, FIG. 18C, and FIG. 18D are illustrations of anexample of front views of a network device, in accordance with anembodiment.

FIG. 19 is a flowchart illustrating an embodiment of a process formodifying a state of a remote electrical device, in accordance with anembodiment.

FIG. 20 is a flowchart illustrating an embodiment of a process formodifying a state of a remote electrical device, in accordance with anembodiment.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, specificdetails are set forth in order to provide a thorough understanding ofembodiments of the invention. However, it will be apparent that variousembodiments may be practiced without these specific details. The figuresand description are not intended to be restrictive.

The ensuing description provides exemplary embodiments only, and is notintended to limit the scope, applicability, or configuration of thedisclosure. Rather, the ensuing description of the exemplary embodimentswill provide those skilled in the art with an enabling description forimplementing an exemplary embodiment. It should be understood thatvarious changes may be made in the function and arrangement of elementswithout departing from the spirit and scope of the invention as setforth in the appended claims.

Specific details are given in the following description to provide athorough understanding of the embodiments. However, it will beunderstood by one of ordinary skill in the art that the embodiments maybe practiced without these specific details. For example, circuits,systems, networks, processes, and other components may be shown ascomponents in block diagram form in order not to obscure the embodimentsin unnecessary detail. In other instances, well-known circuits,processes, algorithms, structures, and techniques may be shown withoutunnecessary detail in order to avoid obscuring the embodiments.

Also, it is noted that individual embodiments may be described as aprocess which is depicted as a flowchart, a flow diagram, a data flowdiagram, a structure diagram, or a block diagram. Although a flowchartmay describe the operations as a sequential process, many of theoperations can be performed in parallel or concurrently. In addition,the order of the operations may be re-arranged. A process is terminatedwhen its operations are completed, but could have additional steps notincluded in a figure. A process may correspond to a method, a function,a procedure, a subroutine, a subprogram, etc. When a process correspondsto a function, its termination can correspond to a return of thefunction to the calling function or the main function.

The term “machine-readable storage medium” or “computer-readable storagemedium” includes, but is not limited to, portable or non-portablestorage devices, optical storage devices, and various other mediumscapable of storing, containing, or carrying instruction(s) and/or data.A machine-readable storage medium or computer-readable storage mediummay include a non-transitory medium in which data can be stored and thatdoes not include carrier waves and/or transitory electronic signalspropagating wirelessly or over wired connections. Examples of anon-transitory medium may include, but are not limited to, a magneticdisk or tape, optical storage media such as compact disk (CD) or digitalversatile disk (DVD), flash memory, memory or memory devices. Acomputer-program product may include code and/or machine-executableinstructions that may represent a procedure, a function, a subprogram, aprogram, a routine, a subroutine, a module, a software package, a class,or any combination of instructions, data structures, or programstatements. A code segment may be coupled to another code segment or ahardware circuit by passing and/or receiving information, data,arguments, parameters, or memory contents. Information, arguments,parameters, data, etc. may be passed, forwarded, or transmitted via anysuitable means including memory sharing, message passing, token passing,network transmission, etc.

Furthermore, embodiments may be implemented by hardware, software,firmware, middleware, microcode, hardware description languages, or anycombination thereof. When implemented in software, firmware, middlewareor microcode, the program code or code segments to perform the necessarytasks (e.g., a computer-program product) may be stored in amachine-readable medium. A processor(s) may perform the necessary tasks.

Systems depicted in some of the figures may be provided in variousconfigurations. In some embodiments, the systems may be configured as adistributed system where one or more components of the system aredistributed across one or more networks in a cloud computing system.

A network may be set up to provide an access device user with access tovarious devices connected to the network. For example, a network mayinclude one or more network devices that provide a user with the abilityto remotely configure or control the network devices themselves or oneor more electronic devices (e.g., appliances) connected to the networkdevices. The electronic devices may be located within an environment ora venue that can support the network. An environment can include, forexample, a home, an office, a business, an automobile, a park, or thelike. A network may include one or more gateways that allow clientdevices (e.g., network devices, access devices, or the like) to accessthe network by providing wired connections and/or wireless connectionsusing radio frequency channels in one or more frequency bands. The oneor more gateways may also provide the client devices with access to oneor more external networks, such as a cloud network, the Internet, and/orother wide area networks.

A local area network, such as a user's home local area network, caninclude multiple network devices that provide various functionalities.Network devices may be accessed and controlled using an access deviceand/or one or more network gateways. One or more gateways in the localarea network may be designated as a primary gateway that provides thelocal area network with access to an external network. The local areanetwork can also extend outside of the user's home and may includenetwork devices located outside of the user's home. For instance, thelocal area network can include network devices such as exterior motionsensors, exterior lighting (e.g., porch lights, walkway lights, securitylights, or the like), garage door openers, sprinkler systems, or othernetwork devices that are exterior to the user's home. It is desirablefor a user to be able to access the network devices while located withinthe local area network and also while located remotely from the localarea network. For example, a user may access the network devices usingan access device within the local area network or remotely from thelocal area network.

In some embodiments, a user may create an account with login informationthat is used to authenticate the user and allow access to the networkdevices. For example, once an account is created, a user may enter thelogin information in order to access a network device in a logicalnetwork.

In some embodiments, an accountless authentication process may beperformed so that the user can access one or more network devices withina logical network without having to enter network device logincredentials each time access is requested. While located locally withinthe local area network, an access device may be authenticated based onthe access device's authentication with the logical network. Forexample, if the access device has authorized access to the logicalnetwork (e.g., a WiFi network provided by a gateway), the networkdevices paired with that logical network may allow the access device toconnect to them without requiring a login. Accordingly, only users ofaccess devices that have authorization to access the logical network areauthorized to access network devices within the logical network, andthese users are authorized without having to provide login credentialsfor the network devices.

An accountless authentication process may also be performed when theuser is remote so that the user can access network devices within thelogical network, using an access device, without having to enter networkdevice login credentials. While remote, the access device may access thenetwork devices in the local area network using an external network,such as a cloud network, the Internet, or the like. One or more gatewaysmay provide the network devices and/or access device connected to thelocal area network with access to the external network. To allowaccountless authentication, a cloud network server may provide a networkID and/or one or more keys to a network device and/or to the accessdevice (e.g., running an application, program, or the like). In somecases, a unique key may be generated for the network device and aseparate unique key may be generated for the access device. The keys maybe specifically encrypted with unique information identifiable only tothe network device and the access device. The network device and theaccess device may be authenticated using the network ID and/or eachdevice's corresponding key each time the network device or access deviceattempts to access the cloud network server.

In some embodiments, a home local area network may include a singlegateway, such as a router. A network device within the local areanetwork may pair with or connect to the gateway and may obtaincredentials from the gateway. For example, when the network device ispowered on, a list of gateways that are detected by the network devicemay be displayed on an access device (e.g., via an application, program,or the like installed on and executed by the access device). In thisexample, only the single gateway is included in the home local areanetwork (e.g., any other displayed gateways may be part of other localarea networks). In some embodiments, only the single gateway may bedisplayed (e.g., when only the single gateway is detected by the networkdevice). A user may select the single gateway as the gateway with whichthe network device is to pair and may enter login information foraccessing the gateway. The login information may be the same informationthat was originally set up for accessing the gateway (e.g., a networkuser name and password, a network security key, or any other appropriatelogin information). The access device may send the login information tothe network device and the network device may use the login informationto pair with the gateway. The network device may then obtain thecredentials from the gateway. The credentials may include a service setidentification (SSID) of the home local area network, a media accesscontrol (MAC) address of the gateway, and/or the like. The networkdevice may transmit the credentials to a server of a wide area network,such as a cloud network server. In some embodiments, the network devicemay also send to the server information relating to the network device(e.g., MAC address, serial number, or the like) and/or informationrelating to the access device (e.g., MAC address, serial number,application unique identifier, or the like).

The cloud network server may register the gateway as a logical networkand may assign the first logical network a network identifier (ID). Thecloud network server may further generate a set of security keys, whichmay include one or more security keys. For example, the server maygenerate a unique key for the network device and a separate unique keyfor the access device. The server may associate the network device andthe access device with the logical network by storing the network ID andthe set of security keys in a record or profile. The cloud networkserver may then transmit the network ID and the set of security keys tothe network device. The network device may store the network ID and itsunique security key. The network device may also send the network ID andthe access device's unique security key to the access device. In someembodiments, the server may transmit the network ID and the accessdevice's security key directly to the access device. The network deviceand the access device may then communicate with the cloud server usingthe network ID and the unique key generated for each device.Accordingly, the access device may perform accountless authentication toallow the user to remotely access the network device via the cloudnetwork without logging in each time access is requested. Also, thenetwork device can communicate with the server regarding the logicalnetwork.

In some embodiments, a local area network may include multiple gateways(e.g., a router and a range extender) and multiple network devices. Forexample, a local area network may include a first gateway paired with afirst network device, and a second gateway paired with a second networkdevice. In the event credentials for each gateway are used to create alogical network, a server (e.g., a cloud network server) may registerthe first gateway as a first logical network and may register the secondgateway as a second logical network. The server may generate a firstnetwork ID and a first set of security keys for the first logicalnetwork. The first set of security keys may include a unique securitykey for the first network device and a unique security key for theaccess device for use in accessing the first network device on the firstlogical network. The server may register the second gateway as thesecond logical network due to differences in the credentials between thefirst gateway and second gateway. The server may assign the secondgateway a second network ID and may generate a second set of securitykeys. For example, the server may generate a unique security key for thesecond network device and may generate a unique security key for theaccess device for use in accessing the second network device on thesecond logical network. The server may associate the first networkdevice and the access device with the first logical network by storingthe first network ID and the first set of security keys in a firstrecord or profile. The server may also associate the second networkdevice and the access device with the second logical network by storingthe second network ID and the second set of security keys in a record orprofile. The server may then transmit the first network ID and the firstset of security keys to the first network device, and may transmit thesecond network ID and the second set of security keys to the secondnetwork device. The two network devices may store the respective networkID and set of security keys of the gateway with which each networkdevice is connected. Each network device may send the respective networkID and the access device's unique security key to the access device. Thenetwork devices and the access device may then communicate with thecloud server using the respective network ID and the unique keygenerated for each device.

Accordingly, when multiple gateways are included in the home local areanetwork, multiple logical networks associated with different networkidentifiers may be generated for the local area network. When the accessdevice is located within range of both gateways in the local areanetwork, there is no problem accessing both network devices due to theability of the access device to perform local discovery techniques(e.g., universal plug and play (UPnP)). However, when the user islocated remotely from the local area network, the access device may onlybe associated with one logical network at a time, which prevents theaccess device from accessing network devices of other logical networkswithin the local area network.

The present disclosure describes a network device for controlling anelectric light or other remote electrical device. The network device mayinclude many of the features found in standard light switches, such as acover plate, a housing, a switching element, and internal wiring. Inaddition to these features, the network device may include a cover platewith embedded cover circuitry for performing advanced functionsunavailable to standard light switches, such as advanced electricalcommunication, data processing, data storing, sensing, displaying,customization, user interfacing, rule creation, rule implementation, andthe like. The cover circuitry may receive electric power via a set ofcontact elements located on the wall-facing side of the cover plate thatelectrically couple with a similar set of contact elements located onthe room-facing side of the housing. The coupling of contact elementsmay form a set of buses that enable data communication between the covercircuitry and circuitry within the housing.

FIG. 1 illustrates an example of a local area network 100. The localarea network 100 includes network device 102, network device 104, andnetwork device 106. In some embodiments, any of the network devices 102,104, 106 may include an Internet of Things (IoT) device. As used herein,an IoT device is a device that includes sensing and/or controlfunctionality as well as a WiFi™ transceiver radio or interface, aBluetooth™ transceiver radio or interface, a Zigbee™ transceiver radioor interface, an Ultra-Wideband (UWB) transceiver radio or interface, aWiFi-Direct transceiver radio or interface, a Bluetooth™ Low Energy(BLE) transceiver radio or interface, an infrared (IR) transceiver,and/or any other wireless network transceiver radio or interface thatallows the IoT device to communicate with a wide area network and withone or more other devices. In some embodiments, an IoT device does notinclude a cellular network transceiver radio or interface, and thus maynot be configured to directly communicate with a cellular network. Insome embodiments, an IoT device may include a cellular transceiverradio, and may be configured to communicate with a cellular networkusing the cellular network transceiver radio. The network devices 102,104, 106, as IoT devices or other devices, may include home automationnetwork devices that allow a user to access, control, and/or configurevarious home appliances located within the user's home (e.g., atelevision, radio, light, fan, humidifier, sensor, microwave, iron,and/or the like), or outside of the user's home (e.g., exterior motionsensors, exterior lighting, garage door openers, sprinkler systems, orthe like). For example, network device 102 may include a home automationswitch that may be coupled with a home appliance. In some embodiments,network devices 102, 104, 106 may be used in other environments, such asa business, a school, an establishment, a park, or any place that cansupport the local area network 100 to enable communication with networkdevices 102, 104, 106. For example, a network device can allow a user toaccess, control, and/or configure devices, such as office-relateddevices (e.g., copy machine, printer, fax machine, or the like), audioand/or video related devices (e.g., a receiver, a speaker, a projector,a DVD player, a television, or the like), media-playback devices (e.g.,a compact disc player, a CD player, or the like), computing devices(e.g., a home computer, a laptop computer, a tablet, a personal digitalassistant (PDA), a computing device, a wearable device, or the like),lighting devices (e.g., a lamp, recessed lighting, or the like), devicesassociated with a security system, devices associated with an alarmsystem, devices that can be operated in an automobile (e.g., radiodevices, navigation devices), and/or the like.

A user may communicate with the network devices 102, 104, 106 using anaccess device 108. The access device 108 may include anyhuman-to-machine interface with network connection capability thatallows access to a network. For example, the access device 108 mayinclude a stand-alone interface (e.g., a cellular telephone, asmartphone, a home computer, a laptop computer, a tablet, a personaldigital assistant (PDA), a computing device, a wearable device such as asmart watch, a wall panel, a keypad, or the like), an interface that isbuilt into an appliance or other device e.g., a television, arefrigerator, a security system, a game console, a browser, or thelike), a speech or gesture interface (e.g., a Kinect™ sensor, aWiimote™, or the like), an IoT device interface (e.g., an Internetenabled device such as a wall switch, a control interface, or othersuitable interface), or the like. In some embodiments, the access device108 may include a cellular or other broadband network transceiver radioor interface, and may be configured to communicate with a cellular orother broadband network using the cellular or broadband networktransceiver radio. In some embodiments, the access device 108 may notinclude a cellular network transceiver radio or interface. While only asingle access device 108 is shown in FIG. 1, one of ordinary skill inthe art will appreciate that multiple access devices may communicatewith the network devices 102, 104, 106. The user may interact with thenetwork devices 102, 104, or 106 using an application, a web browser, aproprietary program, or any other program executed and operated by theaccess device 108. In some embodiments, the access device 108 maycommunicate directly with the network devices 102, 104, 106 (e.g.,communication signal 116). For example, the access device 108 maycommunicate directly with network device 102, 104, 106 using Zigbee™signals, Bluetooth™ signals, WiFi™ signals, infrared (IR) signals, UWBsignals, WiFi-Direct signals, BLE signals, sound frequency signals, orthe like. In some embodiments, the access device 108 may communicatewith the network devices 102, 104, 106 via the gateways 110, 112 (e.g.,communication signal 118) and/or the cloud network 114 (e.g.,communication signal 120).

The local area network 100 may include a wireless network, a wirednetwork, or a combination of a wired and wireless network. A wirelessnetwork may include any wireless interface or combination of wirelessinterfaces (e.g., Zigbee™, Bluetooth™, WiFi™, IR, UWB, WiFi-Direct, BLE,cellular, Long-Term Evolution (LTE), WiMax™, or the like). A wirednetwork may include any wired interface (e.g., fiber, ethernet,powerline ethernet, ethernet over coaxial cable, digital signal line(DSL), or the like). The wired and/or wireless networks may beimplemented using various routers, access points, bridges, gateways, orthe like, to connect devices in the local area network 100. For example,the local area network may include gateway 110 and gateway 112. Gateway110 or 112 can provide communication capabilities to network devices102, 104, 106 and/or access device 108 via radio signals in order toprovide communication, location, and/or other services to the devices.The gateway 110 is directly connected to the external network 114 andmay provide other gateways and devices in the local area network withaccess to the external network 114. The gateway 110 may be designated asa primary gateway. While two gateways 110 and 112 are shown in FIG. 1,one of ordinary skill in the art will appreciate that any number ofgateways may be present within the local area network 100.

The network access provided by gateway 110 and gateway 112 may be of anytype of network familiar to those skilled in the art that can supportdata communications using any of a variety of commercially-availableprotocols. For example, gateways 110, 112 may provide wirelesscommunication capabilities for the local area network 100 usingparticular communications protocols, such as WiFi™ (e.g., IEEE 802.11family standards, or other wireless communication technologies, or anycombination thereof). Using the communications protocol(s), the gateways110, 112 may provide radio frequencies on which wireless enabled devicesin the local area network 100 can communicate. A gateway may also bereferred to as a base station, an access point, Node B, Evolved Node B(eNodeB), access point base station, a Femtocell, home base station,home Node B, home eNodeB, or the like.

The gateways 110, 112 may include a router, a modem, a range extendingdevice, and/or any other device that provides network access among oneor more computing devices and/or external networks. For example, gateway110 may include a router or access point, and gateway 112 may include arange extending device. Examples of range extending devices may includea wireless range extender, a wireless repeater, or the like.

A router gateway may include access point and router functionality, andmay further include an Ethernet switch and/or a modem. For example, arouter gateway may receive and forward data packets among differentnetworks. When a data packet is received, the router gateway may readidentification information (e.g., a media access control (MAC) address)in the packet to determine the intended destination for the packet. Therouter gateway may then access information in a routing table or routingpolicy, and may direct the packet to the next network or device in thetransmission path of the packet. The data packet may be forwarded fromone gateway to another through the computer networks until the packet isreceived at the intended destination.

A range extending gateway may be used to improve signal range andstrength within a local area network. The range extending gateway mayreceive an existing signal from a router gateway or other gateway andmay rebroadcast the signal to create an additional logical network. Forexample, a range extending gateway may extend the network coverage ofthe router gateway when two or more devices on the local area networkneed to be connected with one another, but the distance between one ofthe devices and the router gateway is too far for a connection to beestablished using the resources from the router gateway. As a result,devices outside of the coverage area of the router gateway may be ableto connect through the repeated network provided by the range extendinggateway. The router gateway and range extending gateway may exchangeinformation about destination addresses using a dynamic routingprotocol.

The gateways 110 and 112 may also provide the access device 108 and thenetwork devices 102, 104, 106 with access to one or more externalnetworks, such as the cloud network 114, the Internet, and/or other widearea networks. In some embodiments, the network devices 102, 104, 106may connect directly to the cloud network 114, for example, usingbroadband network access such as a cellular network. The cloud network114 may include a cloud infrastructure system that provides cloudservices. In certain embodiments, services provided by the cloud network114 may include a host of services that are made available to users ofthe cloud infrastructure system on demand, such as registration andaccess control of network devices 102, 104, 106. Services provided bythe cloud infrastructure system can dynamically scale to meet the needsof its users. The cloud network 114 may comprise one or more computers,servers, and/or systems. In some embodiments, the computers, servers,and/or systems that make up the cloud network 114 are different from theuser's own on-premises computers, servers, and/or systems. For example,the cloud network 114 may host an application, and a user may, via acommunication network such as the Internet, on demand, order and use theapplication.

In some embodiments, the cloud network 114 may host a Network AddressTranslation (NAT) Traversal application in order to establish a secureconnection between the cloud network 114 and one or more of the networkdevices 102, 104, 106. For example, a separate secure TransmissionControl Protocol (TCP) connection may be established by each networkdevice 102, 104, 106 for communicating between each network device 102,104, 106 and the cloud network 114. In some embodiments, each secureconnection may be kept open for an indefinite period of time so that thecloud network 114 can initiate communications with each respectivenetwork device 102, 104, or 106 at any time. In some cases, other typesof communications between the cloud network 114 and the network devices102, 104, 106 and/or the access device 108 may be supported using othertypes of communication protocols, such as a Hypertext Transfer Protocol(HTTP) protocol, a Hypertext Transfer Protocol Secure (HTTPS) protocol,or the like. In some embodiments, communications initiated by the cloudnetwork 114 may be conducted over the TCP connection, and communicationsinitiated by a network device may be conducted over a HTTP or HTTPSconnection. In certain embodiments, the cloud network 114 may include asuite of applications, middleware, and database service offerings thatare delivered to a customer in a self-service, subscription-based,elastically scalable, reliable, highly available, and secure manner.

It should be appreciated that the local area network 100 may have othercomponents than those depicted. Further, the embodiment shown in thefigure is only one example of a local area network that may incorporatean embodiment of the invention. In some other embodiments, local areanetwork 100 may have more or fewer components than shown in the figure,may combine two or more components, or may have a differentconfiguration or arrangement of components.

Upon being powered on or reset, the network devices 102, 104, 106 may beregistered with the cloud network 114 and associated with a logicalnetwork within the local area network 100. FIG. 2 illustrates an exampleof a process 200 for registering one or more network devices, such asthe network devices 102, 104, 106 illustrated in FIG. 1. When multiplenetwork devices 102, 104, 106 and gateways 110, 112 are included withina local area network, the network devices and/or gateways may beinstalled at different times, resulting in the techniques described withrespect to FIG. 2 possibly occurring for each network device and/orgateway at different points in time. For example, a user may installnetwork device 102 at a first point in time on a first floor of theuser's house. Gateway 110 may also be located on the first floor,resulting in the network device 102 pairing with gateway 110. The usermay later install gateway 112 and network device 106 on a second floorof the user's home, resulting in the network device 106 pairing withgateway 112.

At 202, a network device may detect one or more gateways upon beingpowered on or reset. In some embodiments, a provisioning process mayoccur when the network device is powered on or reset and detected by anaccess device (e.g., access device 108). During the provisioningprocess, the access device may directly communicate with the networkdevice. In some embodiments, direct communication between networkdevices (e.g., network devices 102, 104, 106) and access device (e.g.,access device 108) may occur using various communications protocols,such as Universal Plug and Play (UPnP), Bluetooth®, Zigbee®,Ultra-Wideband (UWB), WiFi-Direct, WiFi, Bluetooth® Low Energy (BLE),sound frequencies, and/or the like.

The provisioning process may include pairing the network device with agateway and registering the gateway, network device, and access devicewith a server, such as a server located within the cloud network 114.For example, upon being powered on or reset to factory settings, thenetwork device may send or broadcast identification information to oneor more access devices. The identification information may be sentduring a discovery process. For example, the identification informationmay be sent in response to a discovery request from an access device. Insome cases, the identification information may include a name of thenetwork device.

An application, program, or the like that is installed on and executedby the access device may receive the identification information from thenetwork device. When the application on the access device is launched bya user, the access device may display the identification information forselection by the user. Once the network device identificationinformation is selected, the access device may send a signal to thenetwork device indicating that it has been selected. The network devicemay then send to the access device a list of gateways that are detectedby the network device. The access device may receive and display thelist of gateways. In some embodiments, the list of gateways includesmultiple gateways (e.g., gateways 110 and 112) that are located withinthe local area network. The user may select the gateway that the userwishes for the network device to pair. For example, the gateway thatprovides the best signal strength for the network device may beselected. The access device may then prompt the user to enter logininformation that is required for accessing the network signals providedby the selected gateway. For example, the login information may be thesame information that was originally set up to access the gatewaynetwork signals (e.g., when the gateway was initially installed). Onceentered, the access device may send the login information to the networkdevice. The network device may use the login information to pair withthe selected gateway. As one example, network device 102 and networkdevice 104 may be paired with gateway 110, and network device 106 may bepaired with gateway 112.

Once paired with a gateway, the network device may be registered with acloud network (e.g., cloud network 114). For example, the access device(e.g., via the application, program, or the like) may instruct thenetwork device to register with the cloud network upon receivingconfirmation from the network device that it has been successfullypaired with a gateway. At 204, the network device may obtain credentialsfrom the gateway as part of the registration process. For example,network device 102 may obtain credentials from gateway 110. At a same orlater point in time, network devices 104 and 106 may obtain credentialsfrom gateways 110 and 112, respectively. In some embodiments, thecredentials may include a SSID of the local area network and a MACaddress of the gateway. An SSID received from two gateways (e.g.,gateways 110, 112) may be the same due to the gateways both being withinthe same local area network. In some cases, the SSID of the two gatewaysmay be different. The MAC address of each of the gateways may be uniqueto each gateway. As a result of each gateway having a unique MACaddress, the credentials obtained from a gateway may be unique to thatparticular gateway. One of ordinary skill in the art will appreciatethat other credentials may be obtained from a gateway, such as anInternet Protocol address, or the like.

The network device may then send the gateway credentials to the cloudnetwork at 206. For example, the network devices 102, 104, 106 may sendcredentials for the gateway with which each is paired to the serverlocated within the cloud network 114. For example, network device 102may transmit the credentials obtained from gateway 110 to the server,and network device 106 may transmit the credentials obtained fromgateway 112 to the server. In some embodiments, the network device mayalso send information relating to the network device (e.g., MAC address,serial number, make, model number, firmware version, and/or an interfacemodule identifier, or the like) to the server, and/or informationrelating to the access device (e.g., MAC address, serial number,application unique identifier, or the like) to the server. In someembodiments, the communication of the credentials, the network deviceinformation, and/or the access device information sent from the networkdevice to the cloud network server may be in a Hypertext TransferProtocol (HTTP) format, a Hypertext Transfer Protocol Secure (HTTPS)format, a secure Transmission Control Protocol (TCP) format, or thelike. One of ordinary skill in the art will appreciate that othercommunication formats may be used to communicate between the networkdevice and the cloud network server.

Once the credentials, network device information, and/or access deviceinformation are received by the server, the server may register eachgateway as a logical network within the local area network and maygenerate a network ID for each logical network. For example, the servermay register the gateway 110 as a first logical network. During theregistration process, the server may generate a first network ID foridentifying the first logical network. As noted above, one of ordinaryskill in the art will appreciate that any number of gateways may bepresent within the local area network, and thus that any number oflogical networks may be registered for the local area network. Theserver may further generate a first set of security keys forauthenticating the network device and the access device. For example,the server may generate a unique key for the network device 102 and aseparate unique key for the access device 108.

In some embodiments, as previously described, network device 104 mayalso be paired with gateway 110 at the same or a later point in time asthe network device 102. During registration of the network device 104,the server may determine that the access device 108 has already beenregistered with another network device (e.g., network device 102) thatis associated with the same logical network of gateway 110. In suchembodiments, the server may retrieve the first network ID that was usedin registering the first logical network. The server may also generate anew unique security key for the network device 104, and may retrieve theunique key that was previously generated for the access device 108 whenregistering the gateway 110 as the first logical network.

The gateway 112 may also be registered by the server as a second logicalnetwork with a second network ID. A second set of security keys may begenerated for the network device 106 and the access device 108. Forexample, the server may generate a unique security key for the networkdevice 106 and a unique security key for the access device 108 as itrelates to the second logical network. In some embodiments, the gatewaymay 112 be installed at a later point in time after the gateway 110 isinstalled, and thus may be registered as the second logical network atthe later point in time.

A record or profile may then be created for associating each network IDwith the credentials of a corresponding gateway, the correspondingnetwork device(s), and the access device. For example, the server of thecloud network 114 may associate the first network ID with thecredentials of gateway 110. Similarly, the server may associate thesecond network ID with the credentials of gateway 112. In someembodiments, the server performs the association by generating andstoring a record including the network ID, the set of security keys, thegateway credentials, the network devices associated with the network ID(e.g., MAC address or serial number of a network device), the accessdevices associated with the network ID (e.g., MAC address, serialnumber, application unique identifier, or the like), and/or any otherinformation relevant to the network devices and/or gateways. Forexample, the server may store the first network ID and the first set ofsecurity keys in a first record at a first memory space (e.g., in Flash,DRAM, a database, or the like) along with the SSID and MAC address forgateway 110 and an identifier of the network devices 102 and/or 104. Theserver may also store the second network ID and the second set ofsecurity keys in a second record at a second memory space along with theSSID and MAC address for gateway 112 and an identifier of the networkdevice 106. In some embodiments, an example of a network deviceidentifier may include a MAC address of the network device, a serialnumber of the network device, or any other unique identifier.

Each of the first and second network IDs may include a unique number oralphanumeric string generated sequentially or randomly. For example, thefirst time a network device and an associated gateway are registered onthe cloud network 114, the unique network ID for the logical network ofthe gateway may start with 7000000. Each subsequent logical network thatis created may be a sequential increment of the initial network ID(e.g., 7000001, 7000002, 7000003, etc.). As another example, the networkID may be generated by a random or pseudo-random number generator. Oneof ordinary skill in the art will appreciate that other techniques forgenerating a unique ID may be used. The technique used to generate thenetwork IDs may be dependent on a type of database that is included inthe cloud network 114. For example, different databases may havedifferent proprietary mechanisms for creating a unique identifier.

The set of keys generated for each logical network may be generatedusing database specific technique. For example, a MySQL technique may beused to generate the sets of keys. Each key may include a universallyunique identifier (UUID) or a globally unique identifier (GUID). Asdescribed above, for each logical network, the server may generate aunique key for a network device and a separate unique key for an accessdevice.

At 208, the network device may receive the network ID and the set ofsecurity keys. For example, once the server has generated a record orprofile associating the network device 102 with the first logicalnetwork, the server may transmit the first network ID and the first setof security keys to the network device 102. The network device 102 maystore the first network ID and one or more keys of the first set ofkeys. For example, the network device 102 may store the unique securitykey that was created by the server for the network device 102.

As noted previously, the network devices 102, 104, 106 and gateways 110,112 may be installed at different times. For example, in someembodiments, network device 104 may be installed at a point in timeafter the first logical network is created based on the pairing betweengateway 110 and network device 102. In such embodiments, upon beingpowered on, the network device 104 may pair with gateway 110, obtaincredentials from gateway 110, and transmit the credentials to the serverin the cloud network 114 using similar techniques as those describedabove. The server may associate the network device 104 with thepreviously generated first network ID. As described above, the servermay also generate a new unique security key for the network device 104,and may retrieve the unique key that was previously generated for theaccess device 108 when registering the first logical network. Thenetwork device 104 may then receive and store the first network ID andthe security keys from the server.

At 210, the network device may send the network ID and the set ofsecurity keys to the access device. For example, the network device 102may send to the access device 108 the first network ID and the uniquesecurity key generated for the access device 108. The network device 102and the access device 108 may then communicate with the cloud networkserver using the first network ID and each device's unique key. In someembodiments, the network device and the access device may generate asignature using their respective security key. The signature is sent tothe cloud network server along with a communication from the networkdevice or access device. The cloud network server may process thesignature in order to authenticate each device, as described below. Thenetwork device and access device may use different techniques togenerate a signature.

A network device may generate a signature using its uniquely generatedsecurity key. For example, the signature may be expressed as:Authorization=MacAddress“:”Signature“:”ExpirationTime. The Authorizationterm may be an attribute, and the MacAddress, Signature, andExpirationTime terms may include values for the Authorization attribute.In particular, the MacAddress value may include the MAC address of thenetwork device, which may include a unique alphanumeric or numericstring. The network device may retrieve its MAC address from memory andplace it in the MacAddress field. The Signature value may be expressedas: Signature=Base64(HMAC-SHA1(PrivateKey, StringToSign)). The Signaturevalue may include an alphanumeric or numeric string. HMAC-SHA1 is anopen source technique that includes a Hash-based Message AuthenticationCode (HMAC) using a SHA1 hash function. The HMAC-SHA1 technique uses thevalues PrivateKey and StringToSign as inputs. The PrivateKey inputincludes the unique security key that was generated by the server forthe network device. The StringToSign input may be expressed asStringToSign=MacAddress+“fin”+SerialNumber+“\n”+ExpirationTime.Accordingly, the StringToSign input is generated by appending a serialnumber of the network device and an expiration time to the networkdevice's MAC address. The ExpirationTime term may indicate the period oftime for which the signature is valid. In some embodiments, theExpirationTime term may include a current time at which the signature isgenerated plus period of time for which the signature is valid. In oneexample, the ExpirationTime term may be expressed asExpirationTime=Number of seconds since Jan. 1, 1970.

The network device may place the signature in a data packet fortransmission with a communication signal to the cloud network server.The network device may also place the network ID in the data packet. Thesignature and the network ID, if included, may be used by the cloudnetwork server to verify that the network device is associated with thelogical network. In some embodiments, a signature is provided with eachcommunication sent from the network device to the server. Once thesignature is received by the server, the server generates a signatureusing the same expression as that used by the network device. Forexample, the server may retrieve the network device's key and otherrelevant information from storage and generate the signature using thekey and the other information using the expression described above. Theserver then verifies whether the signatures match. Upon determining thatthe signatures match, the server authenticates the network device'scommunication.

An access device may also generate a signature using its uniquelygenerated security key. For example, the access device signature may beexpressed as: Authorization=SDU UniqueId“:”Signature“:”ExpirationTime.The Authorization term may be an attribute, and the SDU UniqueId,Signature, and ExpirationTime terms may include values for theAuthorization attribute. The SDU UniqueId term may include a uniquephone identifier. The SDU UniqueId value may depend on the type ofaccess device that is used and the type of values that may be accessedand/or generated by the type of access device. In some cases, one typeof access device may not allow an application to access a uniqueidentifier of the access device (e.g., a serial number, UUID, or thelike). In such cases, the SDU UniqueId value may include a valuegenerated by an application or program installed on and executed on theaccess device that is used to access the network device. The value maybe unique to the application or program that generated the value. Inother cases, another type of access device may allow an application toaccess a unique identifier of the access device. In such cases, the SDUUniqueId value may include a value that is unique to the access deviceitself, such as a serial number, UUID, or the like. In this example, theaccess device may retrieve the unique value from storage within theaccess device. One of ordinary skill in the art will appreciate thatother unique identifiers may be used to uniquely identify the accessdevice. The Signature value may be expressed as:Signature=Base64(HMAC-SHA1(PrivateKey, StringToSign)). Using thisexpression, the input to the HMAC-SHA1 technique may include aPrivateKey term and a StringToSign term. The PrivateKey input includesthe unique security key that was generated by the server for the accessdevice with regard to a particular logical network. The StringToSigninput may be expressed as StringToSign=UniqueId+“\n”+“\n”+ExpirationTime. The StringToSign value is different from the StringToSign valuegenerated by network device in that no serial number is included.Accordingly, the StringToSign input is generated by appending anexpiration time to the access device's unique identifier. TheExpirationTime term may indicate the period of time for which thesignature is valid, similar to that above for the signature generated bythe network device.

The access device may place the signature in a data packet and maytransmit the data packet to the cloud network server with acommunication signal. The network device may also place the network IDin the data packet. The signature and the network ID, if included, maybe used by the cloud network server to verify that the access device isassociated with the logical network and authorized to communicate withone or more network devices associated with the logical network. In someembodiments, a signature is provided with each communication sent fromthe access device to the server. The cloud server may receive thesignature and may generate a signature using the same expression as thatused by the access device. For example, the server may retrieve theaccess device's key and other relevant information from storage andgenerate the signature using the key and the other information using theexpression described above. The server then verifies whether thesignatures match. Upon determining that the signatures match, the serverauthenticates the access device and allows it to communicate with one ormore of the network devices associated with logical network.

Once the provisioning process is completed, the access device 108 mayaccess the network device 102 locally via the gateway 110 (e.g.,communication signal 118) or remotely via the cloud network 114 (e.g.,communication signal 120). In some embodiments, the communicationbetween the access device 108 and the cloud network 114 may be a HTTP orHTTPS communication. One of ordinary skill in the art will appreciatethat other communication mechanisms may be used to communicate betweenthe access device 108 and the cloud network 114.

The network 100 may enable a user to monitor and/or control operation ofthe devices 102 and 104. For example, a user may monitor and/or controloperation of devices by interacting with a visual interface of thegateway 110 (i.e., a web page for gateway 110) and/or a visual interfacerendered on a display of an access device, such as access device 108. Insome embodiments, an application may be run on the access device. Theapplication may cause the access device to present a graphical interfacethat includes a visual interface for each device accessible on thenetwork 100.

A network device may generate and/or provide a “status” of the networkdevice. In certain embodiments, the status or state of a network devicecan be indicated on a visual interface on the access device, for examplewithin the tile with text and/or graphically. The status of the networkdevice can change based on time (e.g., a period, an interval, or othertime schedule). The status of a network device may be any piece ofinformation pertinent to that particular network device. The status of anetwork device may be any changeable variable of that particular networkdevice. For example, the status of a network device may include a stateof the network device itself (e.g., on or off) or how the network deviceis situated within the network with respect to the other network andother network devices throughout the network. For example, the status ofa network device may refer to the network device's proximity to anothernetwork device and/or its ability to communicate with another networkdevice because of the relative signal strength between the two networkdevices. In certain embodiments, the status can include a value or someother information indicating a unit of measure for a setting or anattribute related to operation of a device connected to the networkdevice. The setting or the attribute can be adjustable within a range ofvalues. For example, the device connected to the network device can be alight bulb and the status can include a value corresponding tobrightness (e.g., a percentage of total brightness) emitted by the lightbulb when the light bulb is powered-on. In another example, the devicecan be a motion sensor and the status can include a value correspondingto sensitivity of the sensor in a range of values between 0 to 100 whenthe sensor is powered on. In yet another example, the device can be afan and the status can include a value corresponding to a speed of thefan on a scale of 0 to 100 when the fan is powered-on.

As described above, upon being powered on or reset, the network devices102 and/or 104 may be registered with the cloud network 114 andassociated with a logical network within the local area network 100.Similarly, upon being powered or switched off or otherwise beingdisconnected from the network 100, the status of the network device 102would be known and stored by a cache (not shown) associated with thenetwork 100. For example, cloud network 114 may include storage (e.g.cache) that stores the status of the network devices within each localarea network 100 it is connected to and/or provides access to. Inanother example, the gateway 110 may include storage that stores thestatus of the network devices within each local area network it isconnected to and/or provides access to. More specifically, the statusstored in the cache may include a status table which indicates thecurrent status of each network device (as of its last communication witheach network device). A status table may include all statuses of eachnetwork device, or individual storage tables for each local area networkor other subset of its network devices/networks. In one embodiment, achange in status may prompt the—network device to push its change instatus to the cloud network 114 for storage or updating of the cloud'sstored status table. In another embodiment, cloud network 114 and/orgateway 110 may continuously (or periodically) communicate with eachnetwork device to check to see if its status has changed.

In some embodiments, a network device (e.g. network device 102 and/or104) may, upon connecting to the local area network 100, check thestatus of the network devices on the network 100. In other embodiments,one-network device may check the status of one or more of the othernetwork devices on the network 100. The network device may seek to checkthe status of another network device or access device for variousreasons, including to display such status(es) to a user on a display orotherwise, to check whether that network device belongs to the samenetwork, to synchronize or coordinate any scheduled executions, toupdate an attribute based on adjustment received among others. Forexample, a network device or user may desire to check various statuseson a connected device, such as power level, timestamped activity history(e.g. temperature for a thermostat, motion for a motion detector, etc.),how long it has been active/turned on, attributes for operation of theconnected device (e.g., a brightness of a lamp, a speed of a fan, or asensitivity of a sensor, etc.), among many others.

In some embodiments, a device, such as the access device 108 shown inFIG. 1 or the gateway 110, connected to the network 100 can communicatean updated status of a network device, such as the network devices 102and/or 104. The updated status can be communicated via the network 100and can include an adjustment that affects a status of the networkdevice. The adjustment can include an amount of change to one or moreattributes, one or more settings, or a combination thereof related tooperation of the network device connected to the network 100. The accessdevice 108 or the gateway 110 can present a graphical interface that canreceive input corresponding to an adjustment to a status of a device. Insome embodiments, the updated status of the network device communicatedto the network 100 can be received by a network device to which theupdated status applies, or can be received by the gateway 110, the cloudnetwork 110, or any other device in communication with the network. Ifthe device cannot directly receive the updated status, it can alsoreceive the updated status from the cloud network 114, the gateway 110,or the other devices in the network 100. In some embodiments, thenetwork device can communicate its updated status to the network 100,which can indicate whether the status has been updated. The updatedstatus can be received by the access device or any other device in thenetwork 100. In some embodiments where the access device is not locatedwithin the network 100, the access device may not immediately receivethe updated status. The updated status can be stored by the cloudnetwork 114 or the gateway 110 for communication to the access device.The status of the network device can indicate whether an adjustment wasmade based on an adjustment in a setting or an attribute transmitted bythe access device. Alternatively, or additionally, the access device canreceive, from any other network device connected to the network 100, astatus update indicating whether the adjustment was in fact made at anetwork device.

A network device seeking to check the status of any other device on thenetwork 100 may communicate with the cloud network 114, to which alldevices on the network 100 are connected either directly or indirectly.Since the cloud network 114 and/or the gateway 110 can store an updatedtable/list of the statuses of each of the network devices 102 and 104within the requesting network's local area network, the cloud network114 and/or gateway 110 may communicate such status data to the networkdevices 102 and 104 and the access device. For example, if-networkdevices 102 and 104 were to each turn on and communicate their statusesto cloud network 114, cloud network 114 may analyze the status ofnetwork devices 102 and 104 and communicate to network devices 102 and104 that they are each connected to the same local area network 100.

FIG. 3 illustrates an example of a network 300, according to embodimentsof the present invention. Specifically, the network 300 can be awireless local area network enabling an access device to communicatewith network devices to control adjustment of attributes related tooperation of the network devices. Network 300 includes network device302, network device 304, network device 306, and network device 308. Thenetwork 300 also includes access device 108. In other words, the network300 may be substantially similar to the network 100 except that accessdevice 108 has been turned on near the network 300, to which it isassociated, or has entered an area to which the network 300 can reach.

When access device 108 can enter the network 300 as shown in FIG. 3,access device 108 may be authenticated based on the access device'sauthentication with the logical network or may otherwise commencecommunication with cloud network 114. Access device 108 may alsocommunicate notification of its presence or other information directlyto other network devices 302-308 within network 300, as shown in FIG. 3by communication paths 330. As noted, such communication may includevarious communications protocols, such as Universal Plug and Play(UPnP), Bluetooth®, Zigbee®, Ultra-Wideband (UWB), WiFi-Direct, WiFi,Bluetooth® Low Energy (BLE), sound frequencies, and/or the like. Forexample, access device 108 may communicate to all other devices innetwork 300, including network device 302, network device 304, networkdevice 306, and network device 308, information/data regarding itsstatus. Such status data may include the fact that it is present andturned on, or other status data/information. At any time that networkdevices 302, 304, 306 and 308 recognize that access device 108 ispresent at network 300, the network devices may communicate back toaccess device 108. For example, the network devices may send anacknowledgement (e.g., ACK signal) back to access device 108 to confirmthat they received the status data sent by access device 108. Thenetwork devices may also send their own status data to access device108.

While network devices 302-308 and access device 108 may each receivecommunication from other network devices around the network 300,including the status of each of those network devices, network devices302-308 and/or access device 108 may be continuously scanning network300 (including, for example, running discovery algorithms) to determinewhether any devices within the network have moved, turned on/off orotherwise added to or subtracted from the network 300, or have otherwisechanged statuses.

Since network devices 302-308 and access device 108 may each receivecommunication from other devices around network 300, including thestatus of each of those devices, each network device within network 300may know the status of each other network device in the network 300. Forexample, access device 108 or devices 302-308 may not be required tocommunicate with cloud network 114 in order to obtain one or more ofsuch statuses. Since cloud network 114 is an external network and may beremote from network 300, communication between network devices withinthe network 300 and cloud 114 may take more time than communicationbetween two devices within network 300. For example, communicationbetween devices within network 300 may take anywhere from 1 millisecondto 100 milliseconds, while communication between a device within network300 and the cloud network 114 may take anywhere from 50 milliseconds to1 second or more). Furthermore, if a network device is retrievinginformation from cloud 114, the request must travel from the networkdevice to cloud network 114, and then the information must travel backfrom cloud network 114 to the network device. This process may doublethe latency caused by retrieving information with cloud 114. Therefore,devices within the network 300 may choose to send and receive/retrievestatuses directly with other devices within the network 300 instead ofcommunicating such information via cloud network 114. When a networkdevice receives status data from another network device on the device'slocal area network 300, it may store that status data so that it mayretrieve and use that status data at a later time.

FIG. 4 illustrates an example of a network 400, according to embodimentsof the present invention. The local area network 400 may include networkdevice 302, network device 304, network device 306, network device 308,and access device 108. FIG. 4 also illustrates that one or more networkdevices 302-308 and/or access device 108 may include a storage device,such as a cache, for storing data, including data regarding its ownstatus and data regarding statuses received from the other deviceswithin local area network 400. For example, access device 108 may, afterbeing powered up, broadcast/send its status to network device 308 viacommunication 434. Network device 308 may store the status data receivedfrom access device 108 until the next time access device 108 updates itsstatus by sending new/updated status data to network device 308. Cachemay be used for storage within network devices 302-308 and/or accessdevices within the local area network 400 so that each of the devicesmay be able to quickly retrieve the data it needs from storage. Anapplication operating on the access device 108 can access the cache toobtain information to display the visual interface for each networkdevice 302-308 registered within the network 400. Although a cachingdevice may be used to store such data within the network and/or accessdevices within the local area network 400, other types of storage may beused.

The cache can contain a known interface list including interfaceinformation for different, known types of devices. The known list caninclude a record for each network device known by the access device 108to exist on the network 400. When an application is run on the accessdevice 108, the access device 108 can access the known interfaces in thecache to present the display of access device 108. The display canpresent one or more visual interfaces, each corresponding to a networkdevice known to exist on the network 400. Each visual interface can begenerated based on a visual interface module corresponding to eachdevice on the network 400. In an example, the display can include avisual interface (e.g., a module tile) for each device in the network400 having an interface in the known interface list.

The cache can also contain known status information about each networkdevice in the known device list. When the application is run on theaccess device 108, the access device 108 can access the known statusinformation in the cache to present a status display. The access device108 can populate each tile with an indicator representing the respectiveknown status information for each device in the known device list. Thestatus display can include an indicator of one or more attributes, oneor more settings, or a combination thereof related to operation of eachdevice in the network 400. For example, the status display can include aspeed of a fan (e.g., a fan speed of 56 in a range of values between 0and 100) of the network device 302 (e.g., a fan), a value of sensitivityof a sensor (e.g., a value of 34 in a range of values 0-100) for thenetwork device 304 (e.g., a motion sensor), a value of brightness (e.g.,65 percent brightness) for the network device 306 (e.g., a light bulb),and a value of temperature (e.g. a slow cooker). Although shown ashaving a single indicator for an attribute or a setting related tooperation of a network device, the status display can present aplurality of indicators corresponding to different attributes and/orsettings related to operation of a network device.

In some embodiments, the cache can include other information about anetwork device. The other information can indicate a device's firmwareversion, last known firmware update status, connectivity to cloudstatus, registration status (e.g., whether the network device has a keyor not), and other such information. The cache can include informationthat could be used for troubleshooting. In embodiments described below,the access device 108 can access status information from another otherdevice on the network 400 and can use that information to update its owncache, update the status display, and/or pass the information to thecloud network 114 and/or the gateway 110 for trouble shooting and/orstorage.

Even though each network device may know and store (e.g. in cache) thestate of each other network device within local area network 400, anetwork device may not know when another network device changes status(e.g. turns/powers off). However, network devices and/or access deviceswithin local area network 400 may broadcast/send any updates in itsstatus to other devices on the network. For example, if network device302 changes status, it may send status data to the other networkdevices, such as network devices 304, 306 and 308 and to access device108. However, network device 302 may not know which devices to updatesince the other devices may change statuses periodically (e.g. turnoff).

Therefore, a network or access device may subscribe to another networkor access device within local area network 400. For example, networkdevices 304, 306 and 308 and access device 108 may subscribe to statusdata notifications/updates from network device 302. Such a subscriptionmay be registered for upon initial connection with network device 302when network device 302 first enters local area network 400 or at anyother time after network device 302 has been associated with local areanetwork 400. Subscriptions may be controlled to last indefinitely or mayexpire after a certain predetermined period of time after initialsubscription. However, network devices may re-subscribe to anothernetwork device before or after their previous subscription has expired.

Subscriptions between network device and/or access devices may beregistered, similar to registering a network device upon initialentrance into the local area network, including security registrationsdescribed herein with respect to FIGS. 1 and 2. For example, a networkdevice may send its unique security key, which it may have stored alongwith its network ID after being registered on the network, to a networkdevice to which it wants to subscribe. However, subscriptions may takeon many other forms, including sending a different form ofidentification to a network device to which a network device wants tosubscribe. However, subscriptions may take on many other forms,including sending a different form of identification to a network deviceto which a network device wants to subscribe.

Upon receiving a subscription from another network device or accessdevice, the device being subscribed to may store a list of the devicesthat subscribed to it. For example, network device 302 may store a listof network devices 304, 306 and 308 and access device 108 after thosedevices subscribe to network device 302. Then, when network device 302undergoes a change in status, network device 302 may send that change instatus to only the devices that had previously subscribed to it butwhere the subscription had not yet expired. Furthermore, according tosome embodiments, the subscription list of a network device may beautomatically updated if that device receives notification that anotherdevice has left the range of the local area network, either from thatdevice itself or from a different device. Therefore, the various deviceswithin a given local area network, such as network 400, each containcontinuously updated statuses of each other device on the network andobtain those statuses and updates through direct communication withoutnecessary use of the cloud.

FIG. 5 illustrates an access device 108 that is located remotely fromnetwork 500 (e.g. local area network), according to embodiments of thepresent invention. Local area network 500 includes gateway 110 andnetwork devices 502 and 504 (which may be, for example, the same as anyof network devices 302-308 in FIGS. 3 and 4), as shown in FIG. 5.However, network 500 may also include a variety of other network devicesand one or more access devices directly connected to network 500.Gateway 110 is connected to cloud network 114, and allows networkdevices 502 and 504 to connect to cloud 114, the internet, or otherexternal networks via gateway 110. In some embodiments, the networkdevices 502 and 504 may include home automation devices that allow auser to access, control, and/or configure various home applianceslocated within the user's home, such as a television, radio, light,microwave, iron, and/or the like.

Access device 108 is not directly connected to network 500. Instead,access device 108 is external to network 500 and may connect to cloudnetwork 114 and to network 500 via cloud network 114. As noted, networkdevices 502 and 504 may change status on a periodic basis. In someembodiments, even when external to and not directly connected to network500, an access device may request to check the status of the devices onthe network. When access device 108 seeks to check the status of anydevice on the network, the access device 108 may transmit/send acommunication 536 to the cloud network 114, to which all devices on thenetwork are connected either directly or indirectly via gateway 110.Since the cloud network 114 stores an updated table/list of the statusesof each of the devices within the requesting access device's network,the cloud network 114 may transmit a communication 538 of such statusdata to the access device 108. For example, after network devices 502and 504 are turned on, authenticated and are a part of network 500,network devices 502 and 504 may communicate their statuses to cloudnetwork 114. Furthermore, any time the status of network devices 502 and504 changes, the device that incurred a status change may push/sendinformation (e.g. an indication) of that status change to cloud network114. Cloud network 114 may store, in cache 526 or otherwise, thestatuses (which may be time stamped in metadata or otherwise) of networkdevices 502 and 504. Therefore, when access device 108 requests fromcloud network 114 the statuses of devices on network 500, cloud 114 maysend its most recently stored/updated statuses to access device 108.

To obtain the most updated status data of devices within network 500,cloud 114 may, upon receiving a request for status data related tonetwork devices 502 and 504, transmit/send a communication 532 (e.g.request, query, etc.) for such status data to network devices 502 and504 via gateway 110. Once network devices 502 and 504 receive thisrequest, network devices 502 and 504 may send a communication 534 (e.g.updated status data) to cloud 114 to replace the previouslystored/cached statuses in cache 526. Upon receipt of updated status data534 from network 500, cloud 114 may send a communication 538 of suchstatus data to the access device 108.

However, the process of cloud network 114 requesting updated statusesfrom network devices 502 and 504 within network 500 may cause latencywithin the system. More specifically, the time required for cloudnetwork 114 to request updated statuses from network devices 502 and 504and to in turn receive updated statuses from network devices 502 and 504may be substantially greater than the time required for cloud network114 to send its currently stored statuses (without being updated) fornetwork devices 502 and 504 to access device 108. For example, of thetotal time required for access device 108 to receive updated statusesfrom cloud network 114, 80% or more of that total time may include cloudnetwork 114 requesting updated statuses from network devices 502 and504. On the other hand, of the total time required for access device 108to receive updated statuses from cloud network 114, 20% or more of thattotal time may include the status data being transmitted from cloudnetwork 114 to access device 108. Since a majority of the processrequired for access device 108 to request and receive status data fornetwork devices 502 and 504 is the transmission of data between cloud114 and network devices 502 and 504, the access device 108 and cloudnetwork 114 may maximize efficiency by minimizing the effect of thetransmission of data between cloud 114 and network devices 502 and 504on the whole process/system.

FIG. 6 illustrates an example of a front view of a network device 600.FIG. 7 illustrates an example of a side view of the network device 600.The network device 600 may include any of the network devices 102, 104,or 106 described herein. In some embodiments, the network device 600 maybe a home automation network device. For example, the network device 600may include a home automation switch that may be coupled with a homeappliance. A user may wirelessly access the network device 600 in orderto access, control, and/or configure various home appliances locatedwithin the user's home. For instance, the user may remotely controlappliances such as a television, radio, light, microwave, iron, spaceheater, wall A/C unit, washer, dryer, fan, and/or the like.

In some embodiments, the network device 600 may include a WiFi enabledswitch that connects home appliances and other electronic devices to acompatible 802.11b/g/n/ac WiFi network. The network device 600 may thusallow users to locally or remotely turn devices on or off from anywhere,program customized notifications, and/or change device status. Thenetwork device 600 may further allow a user to create custom schedulesor have devices respond to sunrise or sunset.

The network device 600 includes an power switch 602 that may bedepressed in order to turn the network device 600 on and off. In someembodiments, a light source may be integrated with or located behind thepower switch. For example, a light-emitting diode (LED) may be locatedon a circuit board under the power button 602. The light source may beilluminated when the network device 600 is powered on, and may not beilluminated when the network device 600 is powered off.

The network device 600 further includes a communications signalindicator 604. The signal indicator 604 may indicate whether the networkdevice 600 has access to a communications signal, such as a WiFi signal.For example, the signal indicator 604 may include a light source (e.g.,a LED) that illuminates when the network device 600 is connected to acommunications signal. The light source may depict different colors orother characteristics (e.g., flashing, dimming, or the like) to indicatedifferent levels of signal strength or mode of operation.

The network device 600 includes a restore button 710. The restore button710 may allow a user to reset the network device 600 to factory defaultsettings. For example, upon being depressed, the restore button 710 maycause all software on the device to be reset to the settings that thenetwork device 600 included when purchased from the manufacturer.

The network device 600 further includes a plug 708 and an outlet 606.The plug 708 allows the network device 600 to be plugged into a wallsocket, such as a socket providing 120V, 220V, or the like. In turn, anappliance may be plugged into the outlet 606. Once the network device600 is registered according to the techniques described above, anappliance plugged into the socket 606 may be controlled by a user usingan access device (e.g., access device 108).

FIG. 8 is an example of a block diagram of the network device 600depicting different hardware and/or software components of the networkdevice 600. As described above with respect to FIGS. 6 and 7, thenetwork device 600 includes the outlet 606, the plug 708, the powerbutton 602, the restore button 710, and the communications signalindicator 604. The network device 600 also includes light source 828associated with the power button 602. As previously described, the lightsource 828 may be illuminated when the network device 600 is powered on.

The network device 600 further includes a relay 810. The relay 810 is aswitch that controls whether power is relayed from the plug 708 to theoutlet 606. The relay 810 may be controlled either manually using thepower button 602 or remotely using wireless communication signals. Forexample, when the power button 602 is in an ON position, the relay 810may be closed so that power is relayed from the plug 708 to the outlet606. When the power button 602 is in an OFF position, the relay 810 maybe opened so that current is unable to flow from the plug 708 to theoutlet 606. As another example, an application or program running on anaccess device may transmit a signal that causes the relay 810 to beopened or closed. For instance, an access application may display agraphical interface on the access device that includes a power button.The user may tap or otherwise select the power button, and the accessapplication may send a communication signal (e.g., over a WiFi network)to the network device 600 instructing the network device 600 to open orclose the relay 810.

The network device 600 further includes flash memory 820 and dynamicrandom access memory (DRAM) 822. The flash memory 820 may be used tostore instructions or code relating to an operating system, one or moreapplications, and any firmware. The flash memory 820 may includenonvolatile memory so that any firmware or other program can be canupdated. In the event the network device 600 loses power, informationstored in the flash memory 820 may be retained. The DRAM 822 may storevarious other types of information needed to run the network device 600,such as all runtime instructions or code.

The network device 600 further includes a CPU/Radio 818. The CPU/Radio818 controls the operations of the network device 600. For example, theCPU/Radio 818 may execute various applications or programs stored in theflash memory 820 and/or the dynamic random access memory (DRAM) 822. TheCPU/Radio 818 may also receive input from the various hardware andsoftware components, interpret the input, and perform one or morefunctions in response to the input. As one example, the CPU/Radio 818may determine whether the power button 602 has been pressed, anddetermines whether the relay 810 needs to be opened or closed. TheCPU/Radio 818 may further perform all communications functions in orderto allow the network device 600 to communicate with other networkdevices, one or more gateways, a cloud network, and/or one or moreaccess devices. While the CPU and radio of the network device 600 areshown to be combined in the CPU/Radio 818, one of ordinary skill in theart will appreciate that, in some embodiments, the CPU and radio may beseparately located within the network device 600. For example, CPUcircuitry may be situated at a separate location on a circuit board fromthe location of radio circuitry, the CPU circuitry may be located on adifferent circuit board from the radio circuitry, or the like. Further,the network device 600 may include multiple radios that are configuredto communicate using one or more communication protocols, such as anycombination of a WiFi™ transceiver radio, a Bluetooth™ transceiverradio, a Zigbee™ transceiver radio, a UWB transceiver radio, aWiFi-Direct transceiver radio, a BLE transceiver radio, and/or any otherwireless network transceiver radio or interface. In some embodiments,the network device 600 does not include a cellular network transceiverradio or interface, and thus may not be configured to directlycommunicate with a cellular network. In some embodiments, the networkdevice 600 may include a cellular network transceiver radio, and may beconfigured to communicate with a cellular network using the cellularnetwork transceiver radio.

The network device 600 may communicate with other devices and/ornetworks via antenna 824. For example, antenna 824 may include a 2.4 GHzantenna, a 5 GHz antenna, or the like, that can transmit and receiveWiFi communications signals. The network device 600 may include othertypes of antennas that can communicate Bluetooth® signals, Zigbee®signals, Ultra-Wideband (UWB) signals, WiFi-Direct signals, BLE signals,and/or the like. In some embodiments, the antenna 824 may be configuredto communicate different types of signals, such as the WiFi signals,Bluetooth® signals, Zigbee® signals, UWB signals, WiFi-Direct signals,BLE signals, and/or the like. In some embodiments, the network device600 may include multiple antennas for communicating the different typesof communication signals. As one example, the network device 600 mayinclude both a 2.4 GHz antenna and a 5 GHz antenna.

The network device 600 further includes a driver 816, a switching powersupply 812, and a voltage regulator 814. The driver 816 may includeinstructions or code that can be used to translate control signals orcommands received from applications running on the DRAM 822 to commandsthat the various hardware components in the network device 600 canunderstand. In some embodiments, the driver 816 may include an ambientapplication running on the DRAM 822. The switching power supply 812 maybe used to transfer power from the outlet in which the plug 708 isconnected to the various loads of the network device 600 (e.g.,CPU/Radio 818). The switching power supply 812 may efficiently convertthe voltage and current characteristics of the electrical power to alevel that is appropriate for the components of the network device 600.For example, the switching power supply 812 may perform AC-DCconversion. In some embodiments, the switching power supply 812 may beused to control the power that is relayed from the plug 708 to theoutlet 606. The voltage regulator 814 may be used to convert the voltageoutput from the switching power supply 812 to a lower voltage usable bythe CPU/Radio 818. For example, the voltage regulator 814 may regulatethe DC voltage from 5V to 3.3V.

In various embodiments, functions may be stored as one or morecomputer-program products, such as instructions or code, in anon-transitory machine-readable storage medium, such as the flash memory820 and/or the DRAM 822. The network device 600 can also comprisesoftware elements (e.g., located within the memory), including, forexample, an operating system, device drivers, executable libraries,and/or other code, such as one or more application programs, which maycomprise computer programs implementing the functions provided byvarious embodiments, and/or may be designed to implement methods and/orconfigure systems, as described herein. Merely by way of example, one ormore procedures described with respect to the processes discussed above,for example as described with respect to FIG. 2, may be implemented ascode and/or instructions executable by a computer (and/or a processorwithin a computer); in an aspect, then, such code and/or instructionscan be used to configure and/or adapt a computer (or other device) toperform one or more operations in accordance with the described methods.Such functions or code may include code to perform the steps describedabove with respect to FIG. 2. The memory, such as the flash memory 820and/or the DRAM 822, may be a processor-readable memory and/or acomputer-readable memory that stores software code (programming code,instructions, etc.) configured to cause a processor(s) within theCPU/Radio 818 to perform the functions described. In other embodiments,one or more of the functions described may be performed in hardware.

A set of these instructions and/or code might be stored on anon-transitory machine-readable storage medium, such as the flash memory820 and/or the DRAM 822. In some cases, the storage medium might beincorporated within a computer system, such as the CPU/Radio 818. Inother embodiments, the storage medium might be separate from a computersystem (e.g., a removable medium, such as a compact disc), and/orprovided in an installation package, such that the storage medium can beused to program, configure and/or adapt a computer with theinstructions/code stored thereon. These instructions might take the formof executable code, which is executable by the network device 600 and/ormight take the form of source and/or installable code, which, uponcompilation and/or installation on the network device 600 (e.g., usingcompilers, installation programs, compression/decompression utilities,etc.) then takes the form of executable code.

It should be appreciated that the network device 600 may have othercomponents than those depicted in FIGS. 6-8. Further, the embodimentshown in the figures are only one example of a network device that mayincorporate an embodiment of the invention. In some other embodiments,network device 600 may have more or fewer components than shown in thefigure, may combine two or more components, or may have a differentconfiguration or arrangement of components.

FIG. 9 is a schematic illustration of a local area network 900 includinga network device 902 that includes an appliance 950. The network device902 can comprise an interface device 904 and the appliance 950 connectedby an appliance interface 908. The appliance interface 908 can include adata connection 918 and a power connection 916. The data connection 918can be a serial connection (e.g., RS-232, USB, or other), or any othersuitable data connection. The interface device 904 can be fully poweredby the appliance 902 through the power connection 916, or can have aseparate source of power.

The appliance 950 can be any suitable electric device, such as a crockpot, space heater, an iron, a washing machine, a dishwasher, a lamp, aradio, a computer, an amplifier, or another electrical device.Additional examples of suitable electrical devices include electricaldevices incorporated into or with non-electrical devices, such as anactuator system in an electrically-actuated deadbolt, a sensing systemin a seat cushion, or other suitable electrical device incorporated intoor with a non-electrical device. The appliance 950 can be adapted tooperate with the interface device 904. The appliance 950 can be anyfinite state machine. The appliance 950 can, but need not, know or storeone or more states related to the appliance. For example, the appliance950 may know or store data related to whether the appliance 950 isturned on, how long the appliance has been on (or off), among otherstatus data.

The interface device 904 can be positioned within the housing of theappliance 950, or can be attached externally to the appliance 950. Theinterface device 904 can be removable from the appliance 950, or can bepermanently installed in or on the appliance 950.

The interface device 904 can be connected to the local area network 900through a network interface. The interface device 904 can be connectedby a wired or wireless connection (e.g., WiFi, Zigbee, or othersdescribed herein or well known). In some embodiments, the interfacedevice 904 can be connected directly to the cloud network 114 through acellular internet connection (e.g., EDGE, LTE, or others).

The interface device 904 can communicate with another network device, anaccess device 108, or another client device through the networkinterface 906. The interface device 904 can transmit a statusinformation signal 910 with status information to the access device 108,and the access device 108 can transmit a network device control signal912 to the interface device 904. The status information signal 910 andthe network device control signal 912 can be transmitted between theinterface device 904 and the access device 108 using atelecommunications network (e.g., a cellular network, or other suitablebroadband network), using a local area network 900 (e.g., through agateway 110), or using the cloud network 114, although such a signal maypass through an intermediary device or network to do so.

The interface device 904 can interpret the network device control signal912 and perform actions based on the contents of the network devicecontrol signal 912. The network device control signal 912 can includecommands that can be performed by the interface device 904 itself. Thenetwork device control signal 912 can also include commands that are tobe performed by the appliance 950. Commands that are to be performed bythe appliance 950 can include commands like turn on or off, set adesired temperature (e.g., heat up or cool down to 215° F. or any othertemperature), or other suitable commands depending on the particularappliance. The interface device 904 can interpret the network devicecontrol signal 912 and can send out a command 922, through the dataconnection 918 of the appliance interface 908, based on the networkdevice control signal 912. The appliance 950 can then perform thecommand indicated in the network device control signal 912.

The interface device 904 can also transmit commands to the appliance 950that are not based on a network device control signal received from theaccess device 108, but are rather based on programming in the interfacedevice 904. Examples of such commands can include commands to update acommunication rate, commands to check a state of the appliance 950,commands to set or get a clock time of the appliance 950, or any othersuitable commands.

The interface device 904 can receive, through the data connection 918 ofthe appliance interface 908, a response (e.g., response 920) to anycommand from the appliance 950. In some examples, the response 920 caninclude an indication that the command 922 was received. In someexamples, the response may include only an indication that a command isreceived (e.g., an ACK). In some examples, the response 920 can includeinformation for some value on the appliance 950, such as an “on/off”state, a serial number, a product identification, a manufactureridentification, a temperature, a time since live, a setting, or anyother value retrievable from the appliance 950. The interface device 904can interpret the value and can send information about the value (e.g.,the state of the appliance is “on,” the temperature of the appliance,the time since the appliance first turned on, or other information) asstatus information (e.g. using status information signal 910) to theaccess device 108. Additionally, the interface device 904 can sendstatus information about itself (e.g., time since live, supplied power,signal strength, and others) as status information (e.g. using statusinformation signal 910) to the access device 108.

The interface device 904 can also use responses (e.g., response 920)from the appliance 950 to perform additional functions at the interfacedevice 904, such as error handling. In some cases, when performing theadditional functions, the interface device 904 does not transmit anystatus information 910 to the access device 108 based on thoseparticular responses.

The access device 108 can include one or more display tiles (e.g.,display tile 914) for displaying information and controls correspondingto the network device 102.

In some embodiments, the interface device 904 can transmit a heartbeatcommand (e.g., command 922) over the data connection 918 to theappliance 902 to determine whether the appliance 950 is working properlyand/or in a state of readiness. If the interface device 904 determinesthat the appliance 950 has had some sort of failure (e.g., the appliance950 sends a response 920 indicating a failure or the interface device904 does not receive any response 920), the interface device 904 cantake corrective action (e.g., restarting the appliance 950 or an elementof the appliance 950), can log the event, or can alert the user).

FIG. 10 depicts a block diagram of a network device including aninterface device 904 attached to an appliance 950 according to oneembodiment. The interface device 904 can include connector 1012 thatinteracts with connector 1032 of the appliance 950.

The interface device 904 can include flash memory 1004 and dynamicrandom access memory (DRAM) 1006. The flash memory 1004 may be used tostore instructions or code relating to an operating system, one or moreapplications, and any firmware. The flash memory 1004 can be used tostore a cache. The flash memory 1004 may include nonvolatile memory sothat any firmware or other program can be can updated. In the event theinterface device 904 loses power, information stored in the flash memory1004 may be retained. The DRAM 1006 may store various other types ofinformation needed to run the interface device 904, such as all runtimeinstructions or code. The flash memory 1004 or DRAM 1006 or acombination thereof may include all instructions necessary tocommunicate with an appliance 950, including all instructions necessaryto communicate using the appliance serial protocol disclosed herein.

The interface device 904 further includes a CPU/Radio 1002. TheCPU/Radio 1002 can control the operations of the interface device 904.For example, the CPU/Radio 1002 may execute various applications orprograms stored in the flash memory 1004 and/or the dynamic randomaccess memory (DRAM) 1006. The CPU/Radio 1002 may also receive inputfrom the appliance 950, interpret the input, and perform one or morefunctions in response to the input. The CPU/Radio 1002 may furtherperform all communications functions in order to allow the interfacedevice 904 to communicate with other network devices, one or moregateways, a cloud network, and/or one or more access devices. Theinterface device 904 may communicate with other devices and/or networksvia antenna 1026. For example, antenna 1026 may include a 2.4 GHzantenna that can transmit and receive WiFi communications signals 1028.The antenna 1026 may include other types of antennas that cancommunicate Bluetooth® signals, Zigbee® signals, Ultra-Wideband (UWB)signals, and/or the like. In some embodiments, the interface device 904may include multiple antennas for communicating different types ofcommunication signals.

The CPU/Radio 1002 can include at least one universal asynchronousreceiver/transmitter (UART) 1010. The CPU/Radio 903 can use the UART1010 to send and receive serial communications. The CPU/Radio 903 cansend data through a transmit line 1022 and a receive data through areceive line 1024. The CPU/Radio 903 can send and receive data throughthe transmit line 1022 and receive line 1024 using a serial protocol,such as RS232. The CPU/Radio 1002 can also include an input/output(GPIO) line 1014, a restore line 1016, an LED 1 line 1018, and an LED 2line 1020. The CPU/Radio 1002 can have additional or fewer lines asnecessary. The GPIO line 1014 can be used for any suitable function,such as powering an indicator light on an appliance 950 or accepting aninput from the appliance 950. A signal sent on the restore line 1016 canbe used to restore the CPU/Radio 1002 and/or the interface device 904 tofactory defaults. The LED 1 line 1018 and LED 2 line 1020 can be used topower first and second LEDs that can be used to indicate variousstatuses, such as whether the interface device has a network connectionand whether the interface device is powered on.

The interface device 904 further includes a voltage regulator 1008. Thevoltage regulator 1008 may be used to convert the voltage output fromthe appliance 950 to a voltage usable by the CPU/Radio 1002. Forexample, the voltage regulator 1008 may regulate the DC voltage from 5Vto 3.3V. The voltage regulator 1008 can be supplied with power from apower line 1030.

Each of the interface lines, including the GPIO line 1014, the restoreline 1016, the LED 1 line 1018, the LED 2 line 1020, the transmit line1022, the receive line 1024, the power line 1030, and any additionallines, can be routed through connector 1012. Connector 1012 can be aproprietary or universal connector. Any appliance 950 to which theinterface device 904 is attached through the connector 1012 can have thenecessary hardware to make use of the interface lines, such as toprovide power to the power line 1030 and to provide the first and secondLEDs that are driven by the LED 1 line 1018 and LED 2 line 1020.

In alternate embodiments, some interface lines are not routed throughthe connector 1012. For example, the power line 1030 can be routed to apower supply attached directly to the interface device 904, and the LED1 line 1018 and LED 2 line 1020 can be routed to first and second LEDslocated within the interface device 904.

In various embodiments, functions may be stored as one or moreinstructions or code in memory, such as the flash memory 1004 and/or theDRAM 1006. The interface device 904 can also comprise software elements(e.g., located within the memory), including, for example, an operatingsystem, device drivers, executable libraries, and/or other code, such asone or more application programs, which may comprise computer programsimplementing the functions provided by various embodiments, and/or maybe designed to implement methods and/or configure systems, as describedherein. Merely by way of example, one or more procedures described withrespect to the processes discussed below may be implemented as codeand/or instructions executable by a computer (and/or a processor withina computer); in an aspect, then, such code and/or instructions can beused to configure and/or adapt a device (e.g. a specialty computer) toperform one or more operations in accordance with the described methods.Such functions or code may include code to perform various stepsdescribed below. The memory, such as the flash memory 1004 and/or theDRAM 1006, may be a processor-readable memory and/or a computer-readablememory that stores software code (programming code, instructions, etc.)configured to cause a processor(s) within the CPU/Radio 1002 to performthe functions described. In other embodiments, one or more of thefunctions described may be performed in hardware.

A set of these instructions and/or code might be stored on acomputer-readable storage medium, such as the flash memory 1004 and/orthe DRAM 1006. In some cases, the storage medium might be incorporatedwithin a computer system, such as the CPU/Radio 1002. In otherembodiments, the storage medium might be separate from a computer system(e.g., a removable medium, such as a compact disc), and/or provided inan installation package, such that the storage medium can be used toprogram, configure and/or adapt a device (e.g. a computer) with theinstructions/code stored thereon. These instructions might take the formof executable code, which is executable by the interface device 904and/or might take the form of source and/or installable code, which,upon compilation and/or installation on the interface device 904 (e.g.,using any of a variety of compilers, installation programs,compression/decompression utilities, etc.) then takes the form ofexecutable code.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

The interface device 904 may have other components than those depictedin FIG. 10. Further, the embodiment shown in the figures are only oneexample of an interface device that may incorporate an embodiment of theinvention. In some other embodiments, interface device 904 may have moreor fewer components than shown in the figure, may combine two or morecomponents, or may have a different configuration or arrangement ofcomponents.

The appliance 950 can have a processor 1034. The processor 1034 can be amicrocontroller, such as a Peripheral Interface Controller (PIC). Theappliance 950 can include a memory 1036 (e.g., a flash memory or other)that is readable by the processor 1034. The memory 1036 can includeinstructions enabling the innate functionality of the appliance 950,such as heating and timing for a crock pot.

The appliance 950 can include a user interface 1038. The user interface1038 can provide buttons, displays, LEDs, knobs, and other input andoutput elements necessary for a user to interact with the appliance 950.For example, a user interface 1038 for a slow cooker can include adisplay, a power button, a temperature adjustment button, and a startbutton. The user interface 1038 can be driven and/or monitored by theprocessor 1034. In some embodiments, the appliance 950 is “headless” orhas no user interface 1038.

The appliance 950 can include a power supply 1040 that can provide powerto the voltage regulator 1038 of the interface device 904 throughconnector 1032, connector 1012, and power line 1030.

The appliance 950 can include an interface device user interfaceextension 1042. The interface device user interface extension 1042 caninclude various input and output elements that are passed directly tothe interface device 904 without being processed by the processor 1034.Examples of input and output elements of the interface device userinterface extension 1042 include LEDs associated with the LED 1 line1018 and LED 2 line 1020, a hardware restore button associated with therestore line 1016, or any other suitable input/output element.

FIG. 11 illustrates a network device 1100 with a virtual interface.Device 1100 includes an interactive display 1105 that can include one ormore virtual options or buttons. In the depicted scenario, display 1105includes five options. In this instance, each option corresponds to ahome location, and each home location can correspond to one or morelights. For example, pressing the “stairs” option can cause one lightbulb in one light fixture in a stairwell to change its on-off state,pressing the “basement” option can cause all lights in all lightfixtures to turn to a particular power state (and a second press couldcause the particular power state to reverse), pressing the “living room”option can cause two bulbs in one light fixture in the living room tochange its power state, etc.

In one instance, one option is temporarily selected. For example,“stairs” may be a default option that is initially selected upondetecting motion or input (e.g., a tap on the display). A user can thenslide another option to a top of the display to temporarily select thatoption (e.g., by touching and dragging on the display). Another input(e.g., a tap on the display or a press of a button on device 1100) cancause the selected option to be confirmed and one or more lightsassociated with the option to be controlled.

In one instance, tapping an option causes display 1105 to change to showinformation and/or detailed options pertaining to the tapped option. Forexample, receiving input corresponding to selection of “Rec Rm” such asby tapping on the display, can cause a screen to be displayed thatindicates that there are 4 light fixtures in the rec room, 2 of whichare on, and present options to change the power state (and/or lightintensity) of individual lights and/or to cause all lights to be set toa same identified power state (and/or light intensity).

FIGS. 12A-12F illustrate a series of example interfaces at a device(e.g., an access device) for receiving user input to define a ruleaccording to an embodiment of the invention. As shown in FIG. 12A, a setof devices for which a rule can be defined can be presented. Eachidentified device can be one that, for example, can serve as a secondarydevice to detect a stimulus and subsequently influence operation ofanother device. In the depicted illustration, each identified device isa switch device and is identified both based on room location andletter. In this example, input is received corresponding to selection of“Entrance Switch A”.

A presentation shown in FIG. 12B identifies the type of stimuli that canbe detected by Entrance Switch A. Entrance Switch A includes two buttons(A and B), each of which can detect and distinguish between a singleclick, a double click and a long click. Switch A can also detect motion.In this example, input is received corresponding to selection of “1click Button A” such that detection of this type of stimulus will serveas a trigger for the rule.

A presentation shown in FIG. 12C identifies a set of master devices. Thelist can include, for example, all network devices, all master networkdevices, all network or master devices of a specific type and/or allnetwork or master devices detected as currently or previously having aload. In this example, Entrance Switch B and Stairs Switch F are omittedfrom the list, as they are not master devices electrically connected toa load. In this example, input is received corresponding to selection ofthree master devices: Entrance Switch A, Living Room Switch C and FoyerOutlet J.

A presentation shown in FIG. 12D identifies potential types of statecontrol. A first option would cause each master device to change itson-off state. Thus, if just prior to detection of a Button A click, theEntrance Switch is on and the Living Room Switch is off, selection ofthe first option would cause the Entrance Switch to turn off and theLiving Room Switch to turn on. A second option is to cause one of thedevices' states to switch from a current state to an opposite state andfor the rest of the devices to switch to or stay in the opposite state.A third option is to cause all of the devices to enter a particularstate (e.g., each device to change to or stay in an “off” state). Inthis example, input is received corresponding to selection of the secondoption.

The second option requires identification of which device will governthe other devices' states. A presentation in FIG. 12E allows forselection of this device (e.g., by clicking on “Entrance Switch A” whichcan cause identifications of each identified master device to bepresented in, for example, a pull-down menu). The presentation furtherallows for selection of an intensity for each of two opposing states.The presentation includes two sliders. In this example, input isreceived corresponding to setting 90% along the first slider and 0%along the second slider.

A presentation shown in FIG. 12F identifies a rule based on the providedinputs. Specifically, when a single click of Button A is detected atEntrance Switch A, it can cause a state of Entrance Switch A to change.When Switch A is in an on state, it will change to an off state and theconverse. For example, when it changes to an on state, the intensitywill be 120%, and when it changes to an off state, the intensity will be0%. The living room switch and foyer outlet will also change (if needed)to match Switch's A updated state. A user can be presented with anopportunity to confirm or modify the rule. Upon confirmation, the rulecan be sent to one, more or all network devices.

The presentations at one or more of FIGS. 12A-12F may be initiated basedon, for example, detection of user input and/or automatic detection. Forexample, a user can provide input corresponding to a request to define arule, after which the presentation of FIG. 12A may be shown. As anotherexample, an automatic detection can detect that a new device joined anetwork, that a device on a network is not associated with a ruletriggered by at least one type of input that can be received at thedevice (or with any rule), or that a characteristic (e.g., location) ofa device changed. The automatic detection can, in some instances,correspond to identifying a device (and, in some instances, an inputtype), which can cause a presentation such as one shown in FIG. 12B or12C to be shown.

FIG. 13 illustrates example views of a network device 1300, with theleft panel showing a front view and the right panel showing a side view.The network device 1300 is stylized as an in-wall light switch stylestructure. The network device 1300 may include any of the networkdevices 102, 104, or 106 described herein. In some embodiments, thenetwork device 1300 may be a home automation network device. Forexample, the network device 1300 may include a home automation switchthat may be coupled with a home appliance. A user may access the networkdevice 1300 in order to control, and/or configure various homeappliances located within the user's home. The user may access thenetwork device 1300 remotely (e.g., wirelessly). For instance, the usermay remotely control appliances such as a television, radio, light,microwave, iron, space heater, wall A/C unit, washer, dryer, fan, and/orthe like.

In some embodiments, the network device 1300 may include a WiFi enabledswitch that connects home appliances and other electronic devices to acompatible 802.11b/g/n/ac WiFi network. The network device 1300 may thusallow users to locally or remotely turn devices on or off from anywhere,program customized notifications, and/or change device status, position,speed or level, among other types of control. The network device 1300may further allow for creation of custom schedules or to enable devicesrespond to sunrise or sunset, indoor or outdoor temperature, audiolevel, light level, sensor conditions, etc.

The network device 1300 can include a primary switching element 1302(e.g., a power switch) that may be depressed in order to change a powerstate of an electrical device drawing power through network device 1300.In the embodiment shown in FIG. 13, primary switching element 1302 isconfigured similar to a decorator style rocker switch, but with apush-button (e.g., momentary) configuration instead of a two-state(i.e., on/off) configuration. Other configurations of a primaryswitching element 1302 can be used. The room-facing side 1320 caninclude one or more primary switching elements 1302, some of which maybe used to send a wireless signal and/or command from the network device1300 to change the power state of an electrical device drawing powerthrough the network device 1300.

In some embodiments, one or more light sources may be integrated with orlocated behind the room-facing side 1320, such as behind a primaryswitching element 1302. For example, a light-emitting diode (LED) may belocated on a circuit board under the primary switching element 1302. Thelight source may be illuminated when the network device 1300 isproviding power to the electrical device, and may not be illuminatedwhen the network device 1300 is not providing power to the electricaldevice, or vice versa. In the embodiment shown in FIG. 13, primaryswitching element 1302 is configured similar to a decorator style rockerswitch, but with a push-button configuration instead of a two-state(i.e., on/off) configuration. Any display can be presented using a lightsource and optionally one or more of a light pipe to direct the lightsource, a mask to provide a user-recognizable pattern to the lightsource, and a lens.

In other embodiments, a variable level switch, such as a dimmer typeswitch, is provided on the room-facing side 1320 of the network device1300. In further embodiments, a touch screen display is provided on theroom-facing side 1320 of the network device 1300, such as to allow amultitude of different inputs, such as to control and program thenetwork device 1300. Including a touch screen display on the networkdevice 1300, for example, optionally provides for the ability to use thenetwork device 1300 as both a network device (102, 104, 106) and anaccess device 108.

The network device 1300 further includes a communications signalindicator. The signal indicator may indicate whether the network device1300 has access to a communications signal, such as a WiFi signal. Forexample, the signal indicator may include a light source (e.g., a LED)that illuminates when the network device 1300 is connected to acommunications signal. The light source may depict different colors orother characteristics (e.g., flashing, dimming, or the like) to indicatedifferent levels of signal strength or mode of operation.

The network device 1300 includes a restore button 1310. The restorebutton 1310 may allow a user to reset the network device 1300 to factorydefault settings. For example, upon being pressed, the restore button1310 may cause all software on the device to be reset to the settingsthat the network device 1300 included when purchased from themanufacturer. Resetting these settings to factory default can includeremoving wireless access settings (e.g., SSID, password, and others),network IDs, security keys, saved rules, stored names and/or images,user settings, and other information.

In some embodiments, the restore button 1310 can respond only to certainpredetermined patterns of being pressed, such as press-and-hold,multiple presses, or multiple presses and hold. In some embodiments, therestore button 1310 can respond to different patterns of being pressedwith different results, such as restoring the network device 1300 tofactory defaults when the button is pressed and held for a certainlength of time (e.g., five seconds), but only removing the wirelessaccess settings (e.g., not removing saved rules, stored names, and/orstored images) when the button is pressed five times in quick successionand then held for ten seconds. In some embodiments, the restore button1310 can be used to only reset the user-defined rules and/or otheruser-defined settings of the network device 1300, without removing anywireless access settings, for example if a user desired to use thenetwork device 1300 within the same network, but for a different purpose(e.g., moving the network device 1300 to a different room).

The restore button 1310 can be located on the room-facing side 1320 suchthat the button is readily accessible by a user while the network device1300 is installed in a wall. In one embodiment, the restore button 1310is located inline with a bezel 1358. The restore button 1310 can beshaped to follow the contour and shape of the bezel 1358 so as to remainunobtrusive. The primary switching element 1302 can extend past thebezel 1358 so that the restore button 1310 is not inadvertently pressed.

The network device 1300 also includes a restart button 1312. The restartbutton 1312 may allow a user to cycle the power of network device 1300.For example, upon being pressed, the restart button 1312 may cause thenetwork device to reboot, simulating disconnection from and reconnectionto line power (e.g., an electrical supply). In some embodiments, therestart button 1312 can physically disconnect power to one or moreelements (e.g., processors) of the network device 1300. In otherembodiments, the restart button 1312 can simply provide a reset signalto one or more elements (e.g., processors) of the network device 1300 tocause such elements to restart.

The restart button 1312 can be located on the room-facing side 1320 suchthat the button is readily accessible by a user while the network device1300 is installed in a wall. In one embodiment, the restart button 1312is located inline with the bezel 1358. The restart button 1312 can beshaped to follow the contour and shape of the bezel 1358 so as to remainunobtrusive. The primary switching element 1302 can extend past thebezel 1358 so that the restart button 1312 is not inadvertently pressed.

The restore button 1310 and restart button 1312 can each be located onan accessible surface (e.g., the room-facing side 1320) of the networkdevice when the network device is recessed in a structure (e.g., mountedin a wall or in an electrical box).

The network device 1300 further includes electric terminals 1308, heredepicted as wires extending from the back of the network device 1300 andcoupled to the wall-facing side 1322, for connection to line power, forproviding electrical power to the network device 1300, and for providingswitchable electrical power to an electrical device. In someembodiments, a variety of electric terminals are useful, includingelectrical wires, screw terminals, barrier terminals, push-in terminalsand the like. Various electrical codes may dictate which electricterminal types are required or permitted for the network device 1300.The electric terminals 1308 allow the network device 1300 to beconnected to line power providing 200V, 120V, or the like. In turn, anelectrical device, such as an outlet, socket, light fixture orappliance, may be connected to the network device 1300. Once the networkdevice 1300 is registered according to the techniques described above, apower state or other controllable aspects of the electrical deviceconnected to the network device 1300 may be controlled by a user usingan access device (e.g., access device 108).

The network device 1300 includes a housing configured to be installed inan electrical box, similar to the placement of conventional lightswitches and electrical outlets. Mounting apertures 1314 are includedfor attaching the network device 1300 to an electrical box, such as anelectrical box located inside a wall. Cover plate holes 1316 areincluded for attaching a wall plate over the network device 1300,similar to the attachment of a switch/wall plate over a conventionallight switch or electrical outlet. The front view of the network device1300 in the left panel of FIG. 13 shows the room-facing side 1320 ofnetwork device 1300. The room-facing side 1320 of the network device1300 and the wall-facing side 1322 of the network device 1300 are bothshown in the right panel of FIG. 13.

In one instance, a power display 1340 can be illuminated to indicatethat the network device 1300 is providing power to the electrical deviceand can be turned off to indicate no power is being provided to theelectrical device. The power display 1340 can comprise a light sourcelocated on a circuit board under the primary switching element 1302, andcan optionally include one or more of a light pipe 1342, a mask 1344,and a lens 1346.

The light pipe 1342 can be used to keep excess light from spilling inundesired directions. The light pipe 1342 can be a hollow piece of blackplastic, a fiber optic tube, or any other suitable structure. The mask1344 can block portions of the light source in order to create apattern. For example, the mask 1344 of a power display 1340 can beshaped to give the light a user-recognizable power button shape. Themask 1344 can be incorporated into the lens 1346. The lens 1346, with orwithout a mask 1344, can be incorporated into room-facing side 1320,such as the primary switching element 1302.

The network device 1300 can include a network status display 1348 thatprovides information about the status of the network device's 1300network connectivity, such as wireless connectivity and signal strength.The network status display 1348 can include a light source, a light pipe1350, and a mask 1352. The mask 1352 can provide a shape to the light,such as the shape of concentric arcs gradually increasing in size,signifying radiating radio waves. Without a lens or other opening, thelight from the network status display 1348 can pass through translucentmaterial of the room-facing side 1320, such as the primary switchingelement 1302. The light source may depict different colors or othercharacteristics (e.g., flashing, dimming, or the like) to indicatedifferent levels of signal strength or mode of operation.

The network device 1300 can include a nightlight display 1354. Thenightlight 1354 can be illuminated whenever the electrical device isturned off or whenever the electrical device is turned off and theambient light is below a preset level. The nightlight display 1354 caninclude a light source and a light pipe 1356. In some embodiments, thenightlight 1354 may not have a light pipe 1356, and can illuminate alarger portion of the room-facing side 1320, such as a larger portion ofthe primary switching element 1302.

Because the various displays (e.g., power display 1340, network statusdisplay 1348, nightlight display 1354, and others) can be locatedanywhere on the room-facing side 1320, the displays can be located onthe primary switching element 1302 (e.g., as shown in FIG. 13), inlinewith a bezel 1358, through a cover, or elsewhere visible to a user whenthe network device 1300 is installed. In some embodiments, each displaycan include one or more light sources capable of providing one or morecolors of light (e.g., a bicolor LED).

FIG. 14 illustrates example views of a network device 1400, with theleft panel showing a front view and the right panel showing a side view.The network device 1400 may include any of the network devices 102, 104,or 106 described herein. The network device 1400 includes a primaryswitching element 1402, a room-facing side 1420, a wall-facing side 1422and a circuit board 1426. Network device 1400 may be similar oridentical to network device 1300, and may include a cover plate 1430.The cover plate 1430 may include clips 1404 for securing the cover plate1430 to a support plate 1406 of the network device 1400. The clips 1404allow the cover plate 1430 to be secured to the support plate 1406without the need to use a screw or other fastener through apertures inthe cover plate, thus creating a clean front. Flexure of the cover plate1430 allows clips 1404 to bend far enough to pass over the bottom and/ortop of the support plate 1406 to remove and attach the cover plate 1430to the support plate 1406. In some embodiments, the cover plate 1430 maybe secured to the support plate 1406 through other means of attachmentbesides clips 1404, such as adhesive, velcro, nails, screws, magnets,suction cups, and the like.

Inclusion of the cover plate 1430 provides for the ability to include acircuit board 1424 within the cover plate 1430. The circuit board 1424located within the cover plate 1430 may communicate with the circuitboard 1426 located within the housing of the network device 1400 via awired connection 1428 or via a wireless connection. In some embodiments,the circuit board 1424 located within the cover plate 1430 may include awireless antenna such that when network device 1400 is mounted in anelectrical box in a wall, the wireless antenna is not placed within thewall or within the electrical box, but is located outside the wall orelectrical box, minimizing or reducing wireless signal interferenceand/or signal degradation due to the electrical box, the wall, andassociated building materials. In addition, placing a wireless antennaat an external location eliminates the requirement to include a wirelessantenna directly on the circuit boards 1424 and 1426, providingadditional space for inclusion of other components. Furthermore, thecircuit board 1424 within the cover plate 1430 allows for inclusion of awide number of sensors, input devices, and output devices in the networkdevice 1400, such as temperature sensors, light sensors, humiditysensors, proximity sensors, touch sensors, audio sensors, chemicalsensors (CO, CO₂, CH₄, etc.), motion sensors, power switching, speakers,cameras, LEDs, biometric sensors, push buttons, display devices, and thelike.

FIGS. 15A-15B illustrate perspective views of a network device 1500,with FIG. 15A showing an assembled view and FIG. 15B showing a partiallyexploded view. The network device 1500 may include any of the networkdevices 102, 104, or 106 described herein. The network device 1500 mayinclude a cover plate 1530 that is attachable to a housing 1501. Thecover plate 1530 may include a room-facing side 1521, a wall-facing side1523, and a cover circuit board 1507, among other components. Thehousing 1501 may include a wall-facing side 1522, a room-facing side1520, electric terminals 1508 for connection to the line power, ahousing circuit board (contained within the housing 1501), and primaryswitching element 1502, among other components.

The network device 1500 may have similar and/or additional features asthose described in reference to FIG. 13 and FIG. 14. For example, one ormore of the components located within the circuit boards of networkdevices 1300 and 1400 may be relocated to the cover circuit board 1507.Relocating certain circuit components, such as a wireless antenna, tothe cover circuit board 1507 may have advantages due to the location ofthe cover plate 1530 outside of the wall in which the network device1500 is mounted. Other circuit components, such as sensors and displays,may be advantageous to include in the cover circuit board 1507 due tothe accessibility of the cover plate 1530 by a user. Furthermore, somecircuit components may be included in the cover circuit board 1507 dueto its modular nature. For example, because the cover plate 1530 may bereplaced more easily than the housing 1501, circuit components thatinvolve quickly evolving technologies may be included in the covercircuit board 1507, and circuit components that involve slowly evolvingtechnologies that need not be replaced as frequently, such as DC powersupplies, may be included in the housing circuit board.

The cover circuit board 1507 located within the cover plate 1530provides additional spatial area for including additional components,such as wireless antennas, switches, touch screen interfaces and thelike. For example, in some embodiments, a wireless antenna may bemounted on the room-facing side 1521 of the cover plate 1530. The covercircuit board 1507 may further include components such as a dataprocessor and wireless transceiver to improve the functionality of thewireless antenna. A transmission line may connect the wireless antennato the wireless transceiver on the cover circuit board 1507 or on thehousing circuit board. In some embodiments, the transmission line maycomprise a coaxial cable, providing an electrically shielded radiofrequency transmission line between the wireless antenna and thewireless transceiver. When the network device 1500 is mounted in anelectrical box placed in a wall, the wireless antenna may be positionedat least partially in front of a plane defined by the room-facingsurface of the wall. This configuration provides the network device 1500with the capability of reducing or minimizing interference for wirelesstransmissions between a wireless antenna to a wireless access point,gateway or other wireless device due to the wall, electrical box orassociated building materials.

The cover circuit board 1507 may be electrically coupled with thehousing circuit board and the electric terminals 1508 via cover contactelements 1527 and housing contact elements 1525 (not visible in FIG. 15due to perspective). When the cover plate 1530 is attached to thehousing 1501 (using clips 1504 or another means of attachment), thecover contact elements 1527 may physically contact the housing contactelements 1525. Because both sets of contact elements are conductors,this provides an electrical connection between the cover circuit board1507 and the housing circuit board, allowing electronic communicationbetween the devices. In some embodiments, either one or both of thecover contact elements 1527 and the housing contact elements 1525comprise a set of metal prongs that are bent in one or two locations toprovide constant physical contact. The contact elements may alsocomprise pressure pins (or Pogo pins) as opposed to traditionalconnectors. The metal prongs shown in FIG. 15B have the advantage ofdealing with potential irregularities in wall surface flatness thatwould interfere with proper mating of connectors. Although the networkdevice 1500 is shown with the cover contact elements 1527 comprising 5metal prongs, the number of contact elements may be greater or less thanthis.

In some embodiments, the network device 1500 may include clips 1504 forsecuring the cover plate 1530 to the housing 1501. The clips 1504 mayhave similar and/or additional features as those discussed in referenceto the clips 1404 of network device 1400. In some embodiments, thenetwork device 1500 includes a protective plate 1509 that may cover aportion or all of the cover circuit board 1507. The protective plate1509 may be a conductive material for reducing electromagneticinterference to the cover circuit board 1507. The protective plate 1509may be grounded or may be a floating conductor. In some embodiments, theprotective plate 1509 may protect the cover circuit board 1507 fromdamage when the cover plate 1530 is being attached or removed from thehousing 1501.

FIG. 15C illustrates an exploded, perspective view of a cover plate1530, in accordance with an embodiment. The cover plate 1530 may havesimilar and/or additional features as those described herein inreference to cover plate 1430. For example, the cover plate 1530 mayinclude a cover circuit board 1507, a protective plate 1509, covercontact elements 1527, and clips 1504.

FIG. 15D illustrates a perspective view of a housing 1501, in accordancewith an embodiment. The housing 1501 may have similar and/or additionalfeatures as those described herein in reference to housings. Forexample, the housing 1501 may include a power display 1540, a primaryswitching element 1502, electric terminals 1508, housing contactelements 1525, and apertures 1531. Although primary switching element1502 is shown as a touch-sensitive dimmer switch, it may be configuredin similar and/or additional ways as those described in reference toprimary switching elements 1302 and 1402. As shown, the primaryswitching element may include a series of electric lights arrangedvertically that indicate a current power state of a remote electricaldevice, such as the power level of a dimmed light. Additionally, thehousing 1501 may include a covering 1529 that may be placed over thehousing contact elements 1525 when a cover plate with enclosed circuitryis not being used. In some embodiments, use of the covering 1529 mayallow the housing 1501 to be aesthetically pleasing without attachingany cover plate. Covering 1529 may also serve to protect housing contactelements 1525 when no cover plate is installed or metal prongs or otherelectrical connectors are positioned in contact with contact elements1525.

FIG. 16 illustrates a side view of a network device 1600 showing onetechnique in which cover contact elements 1627 of cover plate 1630 maycome in physical contact with housing contact elements 1625 of housing1601. The cover contact elements 1625 may comprise a set of metal prongsbent at an angle greater or less than 90 degrees. This may allow themetal prongs to be flexible and remain in constant physical contact withthe housing contact elements 1625, which are shown in FIG. 16 as flatmetal prongs with apertures 1631 for receiving the cover contactelements 1627. In some embodiments, the configurations of the contactelements may be reversed, with the housing contact elements 1625comprising a set of metal prongs bent at an angle greater or less than90 degrees and the cover contact elements 1627 comprising a set of flatmetal prongs with apertures.

FIG. 17 is an example of a block diagram of a network device 1700depicting components and relating to a method of communication of thenetwork device 1700. In some embodiments, a cover circuit board 1707within a cover plate 1730 and a housing circuit board 1705 within ahousing 1701 include UART devices for device-to-device communication.Information may be sent between the circuit boards using buses 1733formed by the cover contact elements being in physical contact with thehousing contact elements, as described herein.

In some embodiments, the buses 1733 comprise 5 separate buses forcommunication. A first bus may be used for transmitting data (T_(x)) bythe cover circuit board 1707 and receiving data (R_(x)) by the housingcircuit board 1705. A second bus may be used for receiving data (R_(x))by the cover circuit board 1707 and transmitting data (T_(x)) by thehousing circuit board 1705. A third bus may be used as a ground and/orneutral signal. A fourth bus may be used as a power signal. The powersignal may be received by the cover circuit board either directly from aline power source or through the housing circuit board 1705. Oneadvantage of receiving the line power signal through the housing circuitboard is that only a single AC/DC power supply may be needed. In someembodiments, electrically coupling with a line power source may bedirect or indirect. Direct electrically coupling with a line power mayinclude direct access to AC voltage provided by the line power, whichmay be 120V or 220V at 60 Hz, or may include direct access to DC voltageprovided by the line power, with no intervening circuit elements. Anindirect electrically coupling with a line power may include access toan AC voltage signal that is separated from the line power by one ormore circuit elements (e.g., resistors, capacitors, inductors,transformers, etc.), or may include access to a DC voltage signal thatis separated from the line power by one or more circuit elements (e.g.,power supplies, AC/DC converters, resistors, capacitors, inductors,etc.). Although the line power is generally regarded as an AC electricalpower source such as a mains power supply, in some embodiments, the linepower may include AC or DC power from an electrical generator, DC powerfrom a battery, and the like.

In some embodiments, the buses 1733 may comprise a fewer number ofindividual buses than 4 or 5. For example, a certain bus in someembodiments may exclusively perform a single function, such astransferring data in one direction, but in other embodiments the bus maycombine different functions. For example, where the communicationbetween the circuit boards is half duplex, devices may take turnsbetween transmitting and receiving data. In full duplex communication,the first and second buses may be combined into a single bus.Furthermore, in some embodiments, a power signal may not be needed wherethe cover circuit board 1707 has an alternative power source, such as abattery power or solar power. In addition, some communication methodsmay not require use of a ground and/or neutral signal.

In some embodiments, a processor within the cover circuit board 1707 maybe configured to receive an input signal related to a sensor readingfrom a sensor located within the cover plate 1730. Obtaining the sensorreading may be triggered by input and may be related to the control of apower state of a remote electrical device, such as a light bulb. Theprocessor may further be configured to transmit a wireless signal tocontrol the state of the remote electrical device. The state of theremote electrical device may include a power state (such as “on”, “off”,or “50% power”), a physical position state (such as “window blindslowered 50%”, “window blinds rotated 75%”, “TV stand raised 100%”, “doorlock in unlocked position”), and the like.

FIGS. 18A-18D illustrate front views of a network device 1800 withvisual interfaces. In some embodiments, the network device 1800 includesa touch screen 1835 on the cover plate 1830 that allows users tointeract with the device using one or more virtual options or buttons.The touch screen 1835 may be partitioned into two or more differentregions as shown in FIGS. 18A and 18D. In the depicted scenario of FIG.18A, the touch screen 1835 includes seven location options on the rightside and three button options on the left side. In this instance, eachlocation option corresponds to a home location, and each button optioncorresponds to a function of the primary switching element 1802.

For example, in some embodiments, a user may first select a group ofremote electrical devices throughout a house using the right side of thetouch screen 1835, such as the “stairs” option and the “porch” option.Second, the user may select how the primary switching element 1802modifies the power state of the selected remote electrical devices, suchas the “on/off” option which may cause all the remote electrical devicesto switch “on” or “off” in unison, regardless of whether their previousstate was “on” or “off”. By way of another example, where the “toggle”option is selected, each press of the primary switching element 1802 maycause the selected remote electrical devices to switch to “on” if theywere previously “off” and to switch to “off” if they were previously“on”. By way of another example, where the “dimmer” option is selected,the primary switching element 1802 may become sensitive to the locationat which the user presses it, allowing the power state of the remoteelectrical devices to be modified according to the typical functionalityof dimmer switches.

The “toggle” option may be implemented using one of several methods. Inone method, when the primary switching element 1802 is pressed, aninterrogation signal may be transmitted wirelessly to determine thecurrent power states of the selected remote electrical devices. After aresponse signal is received indicating the current power states, aninstruction signal may be transmitted to toggle the current powerstates. For example, if a response signal indicates that a remoteelectrical device is “off”, then an instruction signal may betransmitted to modify the power state to “on”. Conversely, if a responsesignal indicates that a remote electrical device is “off”, then aninstruction signal may be transmitted to modify the power state to “on”.The instruction signal may include a series of instructions that whenreceived by a processor within the remote electrical device cause theprocessor to modify the state of the remote electrical deviceaccordingly. For example, an incandescent or LED light bulb with anembedded processor and antenna may receive an instruction signal fromthe network device 1800 that includes instructions to remove voltageand/or current from the wire filament or anode/cathode.

In another method for implementing the “toggle” option, particularly insituations where the remote electrical device may be more sophisticated,a wireless signal is simply transmitted with instructions for a remoteelectrical device to toggle its current power state. The remoteelectrical device then determines its current power state and toggles iteither from “off” to “on” or from “on” to “off”. For example, anincandescent or LED light bulb with an embedded processor and antennamay receive an instruction signal from the network device 1800 thatincludes instructions to toggle its current power state. The light bulbmay determine that it is currently delivering voltage and/or current tothe wire filament or anode/cathode, and in response to thatdetermination it may remove voltage and/or current.

In some embodiments, use of the primary switching element 1802 may notbe needed to modify a power state of a remote electrical device. Forexample, the touch screen 1835 may enable a user to modify a power stateof a remote electrical device by allowing a user to simply press one ofthe location options on the right side. The power state may be modifiedimmediately upon the user pressing one of the location options, or itmay be modified after the user presses both a location option and abutton option. Furthermore, a virtual dimmer switch may be displayed onthe touch screen 1835 to enable a user to more precisely modify a powerstate of a remote electrical device.

In reference to FIG. 18B, the network device 1800 may include a primaryswitching element 1802 situated along a side of the cover plate 1830.The touch screen 1835 may include graphical icons for the locationoptions and/or the button options.

In reference to FIG. 18C, the network device 1800 may include multipleprimary switching elements 1802 performing different functions such asselecting, toggling, and scrolling. The touch screen 1835 may bescrollable by a user in the vertical and/or horizontal direction,allowing a wide range of remote electrical devices to be accessible. Insome embodiments, scrolling in a vertical direction may move throughdifferent levels of a house, and scrolling in a horizontal direction maymove through different remote electrical devices on the current level.

In reference to FIG. 18D, the network device 1800 may include a touchscreen 1835 for receiving user input to define a rule. The functionalityof the network device 1800 to create different rules may be similar tothose described herein, particularly in reference to FIGS. 12A-12F.Rules may be defined in terms of user inputs and sensor readings, aswell as other factors.

FIG. 19 illustrates an example of a process 1900 for modifying a stateof a remote electrical device. Process 1900 may be implemented by any ofthe network devices described herein. In some embodiments, theoperations of process 1900 may be performed by a processor locatedwithin a network device. The processor may be located within a coverplate, a housing, or another location.

At step 1902, a network device may output a representation of anelectronic device on an electronic display. The representation of theelectronic device may be displayed alongside multiple otherrepresentations of other electronic devices, or may be displayed alone.The electronic device may be associated with a state, such as a powerstate or a physical position state. At step 1904, the network device mayreceive input corresponding to a selection of the electronic device. Atstep 1906, the network device may receive input corresponding to amodification of the state of the electronic device. The inputcorresponding to the selection of the electronic device and the inputcorresponding to the modification of the state of the electronic devicemay be received simultaneously or separately.

At step 1908, the network device may transmit a signal corresponding toan instruction, such as an instruction to modify the state of theelectronic device. When received at the electronic device, theinstruction may cause the electronic device to modify the stateaccording to the instruction. In some embodiments, the network devicemay transmit an interrogation signal to determine a current state of theelectronic device, receive a response signal indicating the currentstate of the electronic device, and output the current state of theelectronic device on the electronic display. In some embodiments, step1908 may include transmitting an instruction signal to toggle thecurrent power state of the electronic device.

FIG. 20 illustrates an example of a process 2000 for modifying a stateof a remote electrical device. Process 2000 may be implemented by any ofthe network devices described herein. In some embodiments, theoperations of process 2000 may be performed by a processor locatedwithin a network device. The processor may be located within a coverplate, a housing, or another location.

At step 2002, a network device may determine that a primary switchingelement has been pressed. In some embodiments, the primary switchingelement may transmit a signal to the network device each time it ispressed. In some embodiments, the network device may transmit a signalto the primary switching element to inquire whether or not the primaryswitching element has been pressed. In some embodiments, step 2002 maycomprise the network device determining that a touch screen button hasbeen pressed, instead of the primary switching element. The touch screenbutton may be located on the cover plate as described in reference toFIG. 18A.

At step 2004, the network device may transmit a signal to a sensor. Thesensor may be located within the network device on the room-facing sidetherein, or may be located external to the network device. The networkdevice (or processor therein) and the sensor may communicate viawireless or wired electronic communication. In some embodiments, step2004 is performed only after step 2002 is performed, such that thenetwork device only requests a sensor reading when a user presses theprimary switching element. In some embodiments, step 2004 is entirelyomitted, particularly when the type of sensor being used does notnecessarily transmit a signal but rather is constantly electricallycoupled with a processor. Optionally, sensor readings may beautomatically transmitted without being requested, such as periodicallyor aperiodically.

At step 2006, the network device may receive the sensor reading. In someembodiments, the network device may not directly receive the sensorreading, but may receive a signal that is related to or derived from thesensor reading. For example, the sensor reading may be filtered ordigitized prior to receipt by the network device. The sensor reading maycomprise a scalar value or, in some embodiments, may comprise a morecomplex data structure. For example, the sensor reading may be generatedby a temperature sensor, light sensor, humidity sensor, proximitysensor, touch sensor, motion sensor, camera, biometric sensor, pushbutton, and the like.

At step 2008, the network device determines whether or not aninstruction signal should be transmitted to a remote electrical devicebased on the sensor reading and a rule. As described herein,particularly in reference to FIGS. 12A-12F and 18B, a rule may bedefined. The rule may dictate a type of stimulus that may serve as atrigger for a subsequent action. For example, the subsequent action maybe the transmission of an instruction signal to a remote electricaldevice. Examples of rules used in process 2000 may include any of thefollowing: “IF temperature>70 degrees THEN send instruction signal”, “IFtemperature>70 degrees AND button was pressed THEN send instructionsignal”, and “IF button was pressed THEN send instruction signal”.Therefore, the determination that the instruction signal should betransmitted may be based on a sensor reading and a rule. In someembodiments, the determination may also be based on whether a button waspressed. Alternatively, the determination may be based solely on whethera button was pressed, ignoring the sensor reading.

At step 2010, the network device transmits an instruction signal, suchas an instruction signal to modify the power state of the remoteelectrical device when it is determined that the instruction signalshould be transmitted. As discussed in reference to FIG. 18A, theinstruction signal may comprise instructions to cause the remoteelectrical device to be powered on, powered off, or may cause thecurrent power state of the remote electrical device to toggle fromeither “off” to “on” or from “on” to “off”. The instruction signal maybe sent wirelessly or through a wired connection.

Substantial variations may be made in accordance with specificrequirements. For example, customized hardware might also be used,and/or particular elements might be implemented in hardware, software(including portable software, such as applets, etc.), or both. Further,connection to other access or computing devices such as networkinput/output devices may be employed.

In the foregoing specification, aspects of the invention are describedwith reference to specific embodiments thereof, but those skilled in theart will recognize that the invention is not limited thereto. Variousfeatures and aspects of the above-described invention may be usedindividually or jointly. Further, embodiments can be utilized in anynumber of environments and applications beyond those described hereinwithout departing from the broader spirit and scope of thespecification. The specification and drawings are, accordingly, to beregarded as illustrative rather than restrictive.

In the foregoing description, for the purposes of illustration, methodswere described in a particular order. It should be appreciated that inalternate embodiments, the methods may be performed in a different orderthan that described. It should also be appreciated that the methodsdescribed above may be performed by hardware components or may beembodied in sequences of machine-executable instructions, which may beused to cause a machine, such as a special-purpose processor or logiccircuits programmed with the instructions to perform the methods. Thesemachine-executable instructions may be stored on one or more machinereadable mediums, such as CD-ROMs or other type of optical disks, floppydiskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flashmemory, or other types of machine-readable mediums suitable for storingelectronic instructions. Alternatively, the methods may be performed bya combination of hardware and software.

Where components are described as being configured to perform certainoperations, such configuration can be accomplished, for example, bydesigning electronic circuits or other hardware to perform theoperation, by programming programmable electronic circuits (e.g.,microprocessors, or other suitable electronic circuits) to perform theoperation, or any combination thereof.

While illustrative embodiments of the application have been described indetail herein, it is to be understood that the inventive concepts may beotherwise variously embodied and employed, and that the appended claimsare intended to be construed to include such variations, except aslimited by the prior art.

INCORPORATION BY REFERENCE

The following applications are hereby incorporated by reference in theirentireties for all purposes: U.S. Non-provisional application Ser. No.14/750,786, filed on Jun. 25, 2015, U.S. Non-provisional applicationSer. No. 15/019,525, filed on Feb. 9, 2016, U.S. Non-provisionalapplication Ser. No. 15/019,538, filed on Feb. 9, 2016, U.S. ProvisionalApplication No. 62/087,647, filed on Dec. 4, 2014, U.S. ProvisionalApplication No. 62/087,743, filed on Dec. 4, 2014, U.S. ProvisionalApplication No. 62/024,902, filed on Jul. 15, 2014, U.S. ProvisionalApplication No. 62/020,852, filed on Jul. 3, 2014, U.S. ProvisionalApplication No. 62/018,171, filed on Jun. 27, 2014.

What is claimed is:
 1. A network device comprising: a housing configuredto be mounted into a wall, wherein the housing includes a room-facingside and a wall-facing side, wherein the housing includes electricalconnections for coupling with a line power, and wherein the housingincludes a set of housing electrical contact elements located on theroom-facing side of the housing; and a cover including a room-facingsurface and a wall-facing surface, wherein the wall-facing surface ofthe cover is configured to be removably attached to the room-facing sideof the housing, wherein the cover includes a set of cover electricalcontact elements located on the wall-facing surface of the cover, andwherein the cover includes a cover circuitry configured to receive aninput signal; wherein the cover is attachable to the housing; whereinthe cover circuitry is electrically coupled with e set of coverelectrical contact elements; wherein the set of housing electricalcontact elements are electrically coupleable with the set of coverelectrical contact elements; wherein one or more elements on theroom-facing side of the housing are physically accessible through anopening defined by the cover.
 2. The network device of claim 1, whereinthe cover circuitry is electrically coupled with the line power via theset of housing electrical contact elements and the set of coverelectrical contact elements.
 3. The network device of claim 1, furthercomprising: an antenna located within the cover circuitry forcommunicating with an electrical device.
 4. The network device of claim1, further comprising a processor located within the cover circuitry,wherein the processor is configured to perform operations including:receiving the input signal; and transmitting a signal to modify a stateof an electrical device.
 5. The network device of claim 4, wherein the eof housing electrical contact elements are in physical contact with theset of cover electrical contact elements and form a USB connection. 6.The network device of claim 4, wherein the set of housing electricalcontact elements are in physical contact with the set of coverelectrical contact elements and form a set of buses, the set of busesincluding a first bus, a second bus, and a third bus.
 7. The networkdevice of claim 1, wherein the cover circuitry includes a sensor locatedon the room-facing surface of the cover, wherein the sensor isconfigured to output a sensor reading related to controlling a state ofan electrical device.
 8. The network device of claim 7, wherein thesensor includes a temperature sensor.
 9. A computer-implemented methodcomprising: receiving, by a cover circuitry located within a cover, aninput signal for controlling a state of an electrical device, wherein awall-facing surface of the cover is configured to be removably attachedto a room-facing side of a housing, and wherein the housing isconfigured to be mounted into a wall; and transmitting, by the covercircuitry, a signal to modify the state of the electrical device;wherein the cover is attachable to the housing; wherein a set of housingelectrical contact elements located on the room-facing side of thehousing are electrically coupleable with a set of cover electricalcontact elements located on the wall-facing surface of the cover;wherein the cover circuitry is electrically coupled with the set ofcover electrical contact elements; wherein one or more elements on theroom-facing side of the housing are physically accessible through anopening defined by the cover.
 10. The computer-implemented method ofclaim 9, further comprising: receiving, by the cover circuitry, electricpower from a line power, wherein the electric power is received by thecover circuitry from the line power via the set of housing electricalcontact elements and the set of cover electrical contact elements. 11.The computer-implemented method of claim 9, wherein the cover circuitryincludes an antenna for communicating with the electrical device. 12.The computer-implemented method of claim 9, wherein the set of housingelectrical contact elements are in physical contact with the set ofcover electrical contact elements and form a USB connection.
 13. Thecomputer-implemented method of claim 9, wherein the set of housingelectrical contact elements are in physical contact with the set ofcover electrical contact elements and form a set of buses, wherein theset of buses include a first bus, a second bus, and a third bus.
 14. Thecomputer-implemented method of claim 9, wherein the cover circuitryincludes a sensor located on a room-facing surface of the cover, whereinthe sensor is configured to output a sensor reading related tocontrolling the state of the electrical device.
 15. Thecomputer-implemented method of claim 14, wherein the sensor includes atemperature sensor.
 16. A non-transitory computer-readable mediumcomprising instructions that, when executed by a processor, cause theprocessor to perform operations including: receiving, by a covercircuitry located within a cover, an input signal for controlling astate of an electrical device, wherein a wall-facing surface of thecover is configured to be removably attached to a room-facing side of ahousing, and wherein the housing is configured to be mounted into awall; and transmitting, by the cover circuitry, a signal to modify thestate of the electrical device; wherein the cover is attachable to thehousing; wherein a set of housing electrical contact elements located onthe room-facing side of the housing are electrically coupleable with aset of cover electrical contact elements located on the wall-facingsurface of the cover; wherein the cover circuitry is electricallycoupled with the set of cover electrical contact elements; wherein oneor more elements on the room-facing side of the housing are physicallyaccessible through an opening defined by the cover.
 17. Thenon-transitory computer-readable medium of claim 16, wherein theprocessor is further caused to perform operations including: receiving,by the cover circuitry, electric power from a line power, wherein theelectric power is received by the cover circuitry from the line powervia the set of housing electrical contact elements and the set of coverelectrical contact elements.
 18. The non-transitory computer-readablemedium of claim 16, wherein the cover circuitry includes an antenna forcommunicating with the electrical device.
 19. The non-transitorycomputer-readable medium of claim 18, wherein the set of housingelectrical contact elements are in physical contact with the set ofcover electrical contact elements and form a USB connection.
 20. Thenon-transitory computer-readable medium of claim 18, wherein the set ofhousing electrical contact elements are in physical contact with the setof cover electrical contact elements and form a set of buses, whereinthe set of buses include a first bus, a second bus, and a third bus.